Triple
T26394516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoom-Zoom Stadium |
E663511
|
entity |
| Predicate | sponsoredNameBy |
P60860
|
FINISHED |
| Object | Mazda |
—
|
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: Mazda | Statement: [Zoom-Zoom Stadium, sponsoredNameBy, Mazda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsoredNameBy Context triple: [Zoom-Zoom Stadium, sponsoredNameBy, Mazda]
-
A.
sponsoredNameHolder
chosen
Indicates that one entity holds or uses a name or title under the sponsorship or endorsement of another entity.
-
B.
sponsoredNamePeriod
Indicates a time-bounded period during which an entity’s name is officially sponsored or branded by another party.
-
C.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
D.
sponsorshipNameAdopted
Indicates that an entity has adopted or taken on a specific sponsorship name as its official or recognized designation.
-
E.
sponsoredIn
Indicates that one entity provides financial or material support for another entity’s participation, presence, or activity within a particular context, event, or medium.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610c1b57081909b603c41b3c0e5e0 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:28 p.m.