Triple
T28222709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaídos Stadium |
E711502
|
entity |
| Predicate | governingBodyOfOwner |
P141916
|
FINISHED |
| Object | Municipality of Vigo |
—
|
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: Municipality of Vigo | Statement: [Balaídos Stadium, governingBodyOfOwner, Municipality of Vigo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyOfOwner Context triple: [Balaídos Stadium, governingBodyOfOwner, Municipality of Vigo]
-
A.
governingCompany
Indicates that one company exercises control, authority, or management over another company.
-
B.
governingEntityName
Indicates the name of the organization, body, or authority that governs, manages, or has official control over the referenced entity.
-
C.
organizationTypeOfOwner
Indicates the type or category of organization that owns a given entity.
-
D.
organizationTypeOfGoverningBody
Indicates the type or classification of the organization that serves as the governing body for an entity.
-
E.
governingBodyId
chosen
Indicates the entity that serves as the official governing body responsible for overseeing or managing another entity.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 27, 2026, 10:47 p.m.