Triple
T32005509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakhovskaya Line |
E817253
|
entity |
| Predicate | hasCircleLineConnection |
P35490
|
FINISHED |
| Object | Bolshaya Koltsevaya Line |
—
|
NE NERFINISHED |
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: Bolshaya Koltsevaya Line | Statement: [Kakhovskaya Line, hasCircleLineConnection, Bolshaya Koltsevaya Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCircleLineConnection Context triple: [Kakhovskaya Line, hasCircleLineConnection, Bolshaya Koltsevaya Line]
-
A.
hasCircle
Indicates that one entity possesses, contains, or includes a circle as part of its structure or composition.
-
B.
hasFormerLineConnection
Indicates that there used to be a direct line-based connection (e.g., transport, communication, or utility line) between two entities, but that connection no longer exists.
-
C.
connectedLine
chosen
Indicates that two entities are joined by a continuous line or linear connection.
-
D.
isCircleLineStation
Indicates that a given station is located on or served by the Circle Line.
-
E.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 12:15 a.m.