Triple
T34304123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Football League All-Star Game |
E880261
|
entity |
| Predicate | firstStadium |
P205394
|
FINISHED |
| Object | Balboa Stadium |
E567679
|
NE 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: Balboa Stadium | Statement: [American Football League All-Star Game, firstStadium, Balboa Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStadium Context triple: [American Football League All-Star Game, firstStadium, Balboa Stadium]
-
A.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
B.
leftStadium
Indicates that an entity has departed from or exited a stadium.
-
C.
lastStadium
Indicates that one stadium is the final or most recent stadium associated with a particular entity, such as a team, event, or player.
-
D.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
E.
keyStadium
Indicates that a stadium serves as the primary or main venue associated with a particular entity (such as a team, event, or organization).
- F. None of above. chosen
Provenance (5 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_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e63ba1a8819092fed536cc139861 |
completed | June 20, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:57 a.m.