Triple
T37350524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QNS&L |
E927308
|
entity |
| Predicate | hasRoutePurpose |
P127558
|
FINISHED |
| Object | transport iron ore from mines to ports |
—
|
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: transport iron ore from mines to ports | Statement: [QNS&L, hasRoutePurpose, transport iron ore from mines to ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoutePurpose Context triple: [QNS&L, hasRoutePurpose, transport iron ore from mines to ports]
-
A.
hasNavigationPurpose
Indicates that something exists or is designed specifically to serve a navigational function or goal.
-
B.
routePurpose
chosen
Indicates the intended function or goal that a particular route is designed or used to serve.
-
C.
hasRouteConsideration
Indicates that one entity takes another entity into account when planning, evaluating, or determining a route.
-
D.
hasRouteDestination
Indicates that a route leads to or terminates at a specified destination.
-
E.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 3, 2026, 4:16 p.m.