Triple
T34671053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baumanskaya |
E890378
|
entity |
| Predicate | isOnThroughLineBetween |
P66204
|
FINISHED |
| Object | Kurskaya |
—
|
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: Kurskaya | Statement: [Baumanskaya, isOnThroughLineBetween, Kurskaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnThroughLineBetween Context triple: [Baumanskaya, isOnThroughLineBetween, Kurskaya]
-
A.
liesOnLineBetween
Indicates that one entity is located on the straight line segment connecting two other entities.
-
B.
isJunctionOnLine
Indicates that a particular junction lies on, or is part of, a specified line.
-
C.
isOnBranchOfLine
Indicates that something is located on or belongs to a specific branch of a larger line or route.
-
D.
isBetweenStationsOnLine
chosen
Indicates that something is located or occurs between two stations along the same transit line.
-
E.
isMajorJunctionOnLine
Indicates that a location serves as a primary connecting junction along a particular line or route.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722fb6b248190af46f013f26ef81e |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.