Triple
T27864959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durwood Soccer Stadium |
E704329
|
entity |
| Predicate | hasTenantInPast |
P45212
|
FINISHED |
| Object | FC Kansas City |
—
|
NE NERFINISHED |
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: FC Kansas City | Statement: [Durwood Soccer Stadium, hasTenantInPast, FC Kansas City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTenantInPast Context triple: [Durwood Soccer Stadium, hasTenantInPast, FC Kansas City]
-
A.
hasTenantSince
Indicates that an entity has been the tenant of another entity starting from a specified point in time.
-
B.
hasFormerPrimaryTenant
chosen
Indicates that an entity previously served as the main or principal tenant of another entity, but no longer holds that status.
-
C.
hasOwnerInThePast
Indicates that an entity was owned by another entity at some time in the past, but not necessarily in the present.
-
D.
hasTenantsOverTime
Indicates that an entity has one or more tenants associated with it during specific periods over time.
-
E.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
- F. None of above.
Provenance (3 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 6:20 p.m.