Triple
T20527360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multimodal Operations Division |
E503971
|
entity |
| Predicate | typeOfTransportModesCovered |
P44050
|
FINISHED |
| Object | transit |
—
|
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: transit | Statement: [Multimodal Operations Division, typeOfTransportModesCovered, transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTransportModesCovered Context triple: [Multimodal Operations Division, typeOfTransportModesCovered, transit]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportModeFamily
chosen
Indicates the general category or family of transportation mode to which a specific transport mode belongs (e.g., road, rail, air, water).
-
C.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
D.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
E.
appliesToTransportMode
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular mode of transport.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a0677018819085396cc8795a34e9 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.