Triple
T24118708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M4 railcar |
E597589
|
entity |
| Predicate | usedOnServicePattern |
P2367
|
FINISHED |
| Object | all-stops commuter services |
—
|
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: all-stops commuter services | Statement: [M4 railcar, usedOnServicePattern, all-stops commuter services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnServicePattern Context triple: [M4 railcar, usedOnServicePattern, all-stops commuter services]
-
A.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
-
B.
usedOnPart
Indicates that something is applied to, operates on, or is intended for use with a specific part of a larger object or system.
-
C.
usedOn
chosen
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
D.
currentServicePatternIntroduced
Indicates that the currently operating service pattern was first implemented or put into effect at a specific point in time.
-
E.
usedOnMode
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee1a2608190870ade02495c5ebe |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.