Triple
T4503930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransContainer |
E101285
|
entity |
| Predicate | usesTransportCorridor |
P38051
|
FINISHED |
| Object | Europe–Asia rail routes |
—
|
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: Europe–Asia rail routes | Statement: [TransContainer, usesTransportCorridor, Europe–Asia rail routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTransportCorridor Context triple: [TransContainer, usesTransportCorridor, Europe–Asia rail routes]
-
A.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
B.
usedTransportationInfrastructure
chosen
Indicates that an entity made use of some form of transportation infrastructure (such as roads, railways, or ports) to enable movement or transit.
-
C.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fca7d4819081deb34628e04f00 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.