Triple
T9580517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main North Line |
E231156
|
entity |
| Predicate | primaryFreightType |
P5941
|
FINISHED |
| Object | containerised freight |
—
|
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: containerised freight | Statement: [Main North Line, primaryFreightType, containerised freight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFreightType Context triple: [Main North Line, primaryFreightType, containerised freight]
-
A.
primaryCargoDirection
Indicates the main directional flow or orientation in which the primary cargo is being transported or moved.
-
B.
mainCargo
chosen
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
C.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
D.
primaryTransportModel
Indicates that one transport model is designated as the main or default model used for a given context or entity.
-
E.
primaryCargoOperator
Indicates that an entity serves as the main organization responsible for operating or managing the cargo-related activities of another entity.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99cbe79081909947b4d1389eb015 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.