Triple
T33825276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itabuna |
E866938
|
entity |
| Predicate | mainFootballStadium |
P172608
|
FINISHED |
| Object | Estádio Luiz Viana Filho |
—
|
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: Estádio Luiz Viana Filho | Statement: [Itabuna, mainFootballStadium, Estádio Luiz Viana Filho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFootballStadium Context triple: [Itabuna, mainFootballStadium, Estádio Luiz Viana Filho]
-
A.
footballStadiumLocation
Indicates the relationship specifying where a particular football stadium is geographically located.
-
B.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
C.
keyStadium
chosen
Indicates that a stadium serves as the primary or main venue associated with a particular entity (such as a team, event, or organization).
-
D.
servesFootballStadium
Indicates that one entity functions as a service provider or support facility for a football stadium.
-
E.
WorldCupVenue
Indicates that a location serves or has served as a venue where World Cup matches are held.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7001c04d881909f2541fab62d8b19 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.