Triple
T25581220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MP 59 |
E641244
|
entity |
| Predicate | line11ReplacedBy |
P104961
|
FINISHED |
| Object | MP 14 |
—
|
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: MP 14 | Statement: [MP 59, line11ReplacedBy, MP 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line11ReplacedBy Context triple: [MP 59, line11ReplacedBy, MP 14]
-
A.
lineReplaced
chosen
Indicates that one line has been substituted or superseded by another line, typically in a versioning, editing, or modification context.
-
B.
replacedByOnOrangeLine
Indicates that one entity on the Orange Line has been superseded or substituted by another entity on that same line.
-
C.
subLine
Indicates that one line is a subordinate or component segment of another, typically representing a part–whole or hierarchical relationship between lines.
-
D.
line1Section
Indicates that one entity is a specific section or segment of another entity referred to as "line1."
-
E.
lineOriginallyServed
Indicates that a particular transit or service line initially operated or provided service to a specified location, route, or 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f934be208190aed5a7f6a44b6b83 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 4:12 p.m.