Triple
T22811262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beverly D. Stakes |
E564680
|
entity |
| Predicate | formerVenueLocation |
P149814
|
FINISHED |
| Object | Arlington Heights, Illinois |
—
|
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: Arlington Heights, Illinois | Statement: [Beverly D. Stakes, formerVenueLocation, Arlington Heights, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerVenueLocation Context triple: [Beverly D. Stakes, formerVenueLocation, Arlington Heights, Illinois]
-
A.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
-
B.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
C.
venueFormerName
Indicates that a venue previously had a different official name than it has currently.
-
D.
legacyVenue
Indicates that a venue has historical or long-standing significance, often preserved or recognized due to its past importance or enduring role.
-
E.
replacedVenueLocation
Indicates that one venue location has been superseded or taken over by another venue location.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d60186881908f6cb609c536dc91 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:32 p.m.