Triple
T3706424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cívitas Metropolitano Stadium |
E80903
|
entity |
| Predicate | mainStandFeature |
P41649
|
FINISHED |
| Object | continuous ring-shaped roof |
—
|
LITERAL 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: continuous ring-shaped roof | Statement: [Cívitas Metropolitano Stadium, mainStandFeature, continuous ring-shaped roof]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStandFeature Context triple: [Cívitas Metropolitano Stadium, mainStandFeature, continuous ring-shaped roof]
-
A.
mainStandName
Indicates that one entity is the primary or official name of a stand associated with another entity.
-
B.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
primarySettingFeature
Indicates that a particular feature is the main or defining characteristic of a setting.
-
D.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
E.
featuresStar
Indicates that one entity prominently includes or showcases another entity as a main star or featured performer.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54ce1788190ac000793cbdaba48 |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.