Triple
T12431516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M104 bus |
E297039
|
entity |
| Predicate | formerModeOfTransport |
P101439
|
FINISHED |
| Object | streetcar |
—
|
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: streetcar | Statement: [M104 bus, formerModeOfTransport, streetcar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerModeOfTransport Context triple: [M104 bus, formerModeOfTransport, streetcar]
-
A.
previousTransport
Indicates that one entity served as the immediately preceding mode or instance of transport for another entity in a sequence of movements or journeys.
-
B.
formerTransport
chosen
Indicates that an entity previously served as a means of transportation for another entity but no longer does so.
-
C.
replacedModeOfTransport
Indicates that one mode of transport has been substituted or superseded by another in fulfilling a given travel or transport function.
-
D.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
E.
modeOfTransportBeforeStranding
Indicates the means of transportation an entity was using immediately prior to becoming stranded.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.