Triple
T15951985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVM-430 |
E386838
|
entity |
| Predicate | replacesLinesideSignals |
P80083
|
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: [TVM-430, replacesLinesideSignals, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesLinesideSignals Context triple: [TVM-430, replacesLinesideSignals, yes]
-
A.
lineReplaced
Indicates that one line has been substituted or superseded by another line, typically in a versioning, editing, or modification context.
-
B.
interchangeWithLine
Indicates that one entity can be transferred or switched to another specific line, such as a route, track, or service line, at a given point.
-
C.
replacedRollingStock
Indicates that one rolling stock asset has been substituted or superseded by another in service or operational use.
-
D.
replacedSignageType
chosen
Indicates that one type of signage has been substituted or superseded by another type of signage.
-
E.
rerLines
Indicates that one entity represents a railway or transit line that is operated, served, or defined by the other entity.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.