Triple
T3640797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Stadium |
E77181
|
entity |
| Predicate | hostedTeamFrom |
P49965
|
FINISHED |
| Object | Dallas Cowboys from 1971 to 2008 |
—
|
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: Dallas Cowboys from 1971 to 2008 | Statement: [Texas Stadium, hostedTeamFrom, Dallas Cowboys from 1971 to 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedTeamFrom Context triple: [Texas Stadium, hostedTeamFrom, Dallas Cowboys from 1971 to 2008]
-
A.
hostTeam
Indicates that one team serves as the host (home) team in relation to a particular game, match, or event.
-
B.
managedTeamFrom
Indicates that one entity led, directed, or supervised a team originating from or based in another specified entity.
-
C.
hostNationTeam
Indicates that a team is representing the nation that is hosting the event or competition.
-
D.
attractsTeamsFrom
Indicates that an entity draws or pulls in teams from another specified entity or location.
-
E.
hostedTeamAchievement
Indicates that an entity organized or hosted an event or context in which a team achieved a particular accomplishment.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc357c3308190bd8801d68244a53e |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:24 p.m.