Triple
T8016488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazan Arena |
E186629
|
entity |
| Predicate | hasLocationCoordinate |
P10760
|
FINISHED |
| Object | approximate latitude 55.82 N |
—
|
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: approximate latitude 55.82 N | Statement: [Kazan Arena, hasLocationCoordinate, approximate latitude 55.82 N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationCoordinate Context triple: [Kazan Arena, hasLocationCoordinate, approximate latitude 55.82 N]
-
A.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
B.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
C.
hasCoordinateRole
Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
-
D.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
E.
hasApproximateCoordinates
chosen
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df37a00819088780e5461bc5b41 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.