Triple
T34304134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Football League All-Star Game |
E880261
|
entity |
| Predicate | 1965GameRelocatedTo |
P1660
|
FINISHED |
| Object | Houston, Texas |
—
|
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: Houston, Texas | Statement: [American Football League All-Star Game, 1965GameRelocatedTo, Houston, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1965GameRelocatedTo Context triple: [American Football League All-Star Game, 1965GameRelocatedTo, Houston, Texas]
-
A.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
B.
relocatedCompanyHeadquartersTo
Indicates that a company moved its main headquarters from a previous location to a new specified location.
-
C.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
D.
originalBrownsRelocatedTo
Indicates that the original Cleveland Browns franchise moved its operations and identity to another city or team location.
-
E.
after1960LocatedIn
Indicates that the entity was located in the specified place at some point after the year 1960.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.