Triple
T26684883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Арена «Шайба» |
E672715
|
entity |
| Predicate | категорияСооружения |
P96717
|
FINISHED |
| Object | олимпийский объект |
—
|
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: олимпийский объект | Statement: [Арена «Шайба», категорияСооружения, олимпийский объект]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: категорияСооружения Context triple: [Арена «Шайба», категорияСооружения, олимпийский объект]
-
A.
buildings
Indicates that one or more buildings are associated with, located at, or relevant to the referenced entity.
-
B.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
C.
типСтроения
chosen
Indicates the specific kind or category of building or structure associated with an entity.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
notableConstructionCenter
Indicates that a place serves as a significant hub or focal point for construction activity or construction-related operations.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6173d46088190859dd8292d078771 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:22 a.m.