Triple
T34888504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal–Quebec City |
E1006216
|
entity |
| Predicate | hasMajorModeOfTransport |
P70707
|
FINISHED |
| Object | rail |
—
|
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: rail | Statement: [Montreal–Quebec City, hasMajorModeOfTransport, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorModeOfTransport Context triple: [Montreal–Quebec City, hasMajorModeOfTransport, rail]
-
A.
hasPrimaryTransportationMode
chosen
Indicates the main or most frequently used mode of transportation associated with an entity.
-
B.
hasSecondaryTransportationMode
Indicates that an entity is associated with an additional, non-primary mode of transportation it can use or provide.
-
C.
hasTransportationAbove
Indicates that one entity provides or has transportation infrastructure or services located above another entity (e.g., elevated roads, railways, or transit lines).
-
D.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
E.
hasPublicTransitMode
Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01d339feac8190a3de56b24db67163 |
completed | May 11, 2026, 1:01 p.m. |
| PD | Predicate disambiguation | batch_6a01d2bc1f408190a04869f95e6941ee |
completed | May 11, 2026, 12:59 p.m. |
Created at: May 3, 2026, 4 p.m.