Triple
T24476282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pravoberezhnaya Line |
E617240
|
entity |
| Predicate | hasRightBankOrientation |
P37323
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pravoberezhnaya Line, hasRightBankOrientation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightBankOrientation Context triple: [Pravoberezhnaya Line, hasRightBankOrientation, yes]
-
A.
isOnLeftBank
Indicates that one entity is located on the left bank (left side) of a river or similar waterway relative to its flow direction.
-
B.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
C.
hasShoreOrientation
Indicates the directional orientation of a shoreline relative to a reference frame (e.g., compass direction or facing).
-
D.
bodySideOrientation
chosen
Indicates the spatial relationship of an entity with respect to the left, right, or bilateral side of a body.
-
E.
hasRegionalOrientation
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2994820f0819096f04d72ee2f4258 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.