Triple
T23484030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffs |
E570480
|
entity |
| Predicate | homeCityFootball |
P150859
|
FINISHED |
| Object | Boulder, Colorado |
—
|
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: Boulder, Colorado | Statement: [Buffs, homeCityFootball, Boulder, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCityFootball Context triple: [Buffs, homeCityFootball, Boulder, Colorado]
-
A.
cityOfHomeStadium
Indicates the city in which a given home stadium is located.
-
B.
occasionalHomeGroundCity
Indicates that a location serves as a non-primary or infrequent home ground city for an entity, such as a sports team or organization.
-
C.
cityFootballContext
Indicates a contextual relationship where an event, action, or entity is specifically situated within the domain of football as it relates to a particular city (e.g., its clubs, matches, or local football culture).
-
D.
homeCityOf
chosen
Indicates that a particular city is the primary place of residence or origin for a given person or organization.
-
E.
homeMatchCity
Indicates that the entity’s home location is situated within the specified city.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a752c678819087e5c50b8cf87d3d |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.