Triple
T31675187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хорошёвская |
E808379
|
entity |
| Predicate | имеетПереход |
P174429
|
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.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
B.
transitionedThrough
Indicates that an entity passed from one state, phase, or condition to another by way of an intermediate state, phase, or condition.
-
C.
hasTransitionTo
Indicates that one state, condition, or entity can change or move into another specified state, condition, or entity.
-
D.
hasNotableTransition
Indicates that an entity undergoes or is associated with a significant change, shift, or transformation in state, condition, or role.
-
E.
hasJump
Indicates that an entity performs or is capable of performing a jumping action.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: April 30, 2026, 11:02 p.m.