Triple
T33565044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Bosque de Para Uno |
E859733
|
entity |
| Predicate | hasSponsorshipNameOfStadium |
P84804
|
FINISHED |
| Object | Estadio Tigo Manuel Ferreira |
—
|
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: Estadio Tigo Manuel Ferreira | Statement: [El Bosque de Para Uno, hasSponsorshipNameOfStadium, Estadio Tigo Manuel Ferreira]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSponsorshipNameOfStadium Context triple: [El Bosque de Para Uno, hasSponsorshipNameOfStadium, Estadio Tigo Manuel Ferreira]
-
A.
sponsorOfStadiumName
chosen
Indicates that an entity serves as the naming-rights sponsor for a particular stadium.
-
B.
stadiumNamesake
Indicates that one entity serves as the namesake or is the person/thing after which a particular stadium is named.
-
C.
homeStadiumCurrentSponsorshipName
Indicates the name of the current sponsorship associated with a team's home stadium.
-
D.
stadiumOfficialName
Indicates the formal, legally recognized name assigned to a stadium.
-
E.
associatedWithStadiumNickname
Indicates that an entity is connected to or commonly referred to by a particular stadium nickname.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 1, 2026, 1:40 a.m.