Triple
T25581231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MP 59 |
E641244
|
entity |
| Predicate | statusOnLine6 |
P169216
|
FINISHED |
| Object | largely withdrawn from regular service |
—
|
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: largely withdrawn from regular service | Statement: [MP 59, statusOnLine6, largely withdrawn from regular service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOnLine6 Context triple: [MP 59, statusOnLine6, largely withdrawn from regular service]
-
A.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
B.
stationOnLine
Indicates that a particular station is located on or served by a specific transit line.
-
C.
line8Status
Indicates the status or condition associated with the eighth line in a sequence, record, or structured data set.
-
D.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
E.
statusInterface
Indicates that an entity serves as, or is associated with, an interface that reports or reflects its current status.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 21, 2026, 4:12 p.m.