Triple
T9717885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashirskaya |
E235387
|
entity |
| Predicate | hasFormerLineRole |
P90413
|
FINISHED |
| Object | terminus of Kakhovskaya Line |
—
|
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: terminus of Kakhovskaya Line | Statement: [Kashirskaya, hasFormerLineRole, terminus of Kakhovskaya Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerLineRole Context triple: [Kashirskaya, hasFormerLineRole, terminus of Kakhovskaya Line]
-
A.
hasFormerAnchor
Indicates that an entity previously served as an anchor (e.g., host or main presenter) for another entity, but no longer holds that role.
-
B.
hasEarlyRoleFor
Indicates that one entity holds or performs an initial or early-stage role in relation to another entity or process.
-
C.
hasDeFactoLine
Indicates that there exists an unofficial or non-legally recognized boundary or demarcation line functioning in practice between the related entities.
-
D.
hasFormerCode
Indicates that an entity was previously identified or referenced by an earlier code that is no longer current.
-
E.
hasLowerLevelLine
Indicates that one line is positioned or ranked below another line within a hierarchical or layered structure.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e3ea61081908a5671fc5be9a738 |
completed | April 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:20 p.m.