Triple
T23521694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentine football league system |
E574523
|
entity |
| Predicate | includesInteriorZone |
P153078
|
FINISHED |
| Object | Argentine interior regions |
—
|
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: Argentine interior regions | Statement: [Argentine football league system, includesInteriorZone, Argentine interior regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesInteriorZone Context triple: [Argentine football league system, includesInteriorZone, Argentine interior regions]
-
A.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
C.
hasInteriorBehavior
Indicates that an entity exhibits a particular behavior or set of behaviors within its internal or enclosed space.
-
D.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
E.
zonedUse
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
- F. None of above. chosen
Provenance (4 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa873ad48190a86807bd4f26df82 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:08 p.m.