Triple
T749380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polo Grounds |
E15412
|
entity |
| Predicate | primaryTenantTo |
P18749
|
FINISHED |
| Object | 1957 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1957 | Statement: [Polo Grounds, primaryTenantTo, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTenantTo Context triple: [Polo Grounds, primaryTenantTo, 1957]
-
A.
primaryClient
Indicates that one entity serves as the main or most important client associated with another entity.
-
B.
primaryAuthorityFor
Indicates that one entity serves as the main or leading source of control, responsibility, or decision-making power for another entity or domain.
-
C.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
D.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
E.
divisionOfPrimaryTenant
Indicates that one entity is a division or sub-unit that belongs to or operates under the primary tenant entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6304e0c8190827fb57c5cac2da9 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a58c0a84819094f07658dc651b36 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.