Triple
T14462313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZHP |
E358612
|
entity |
| Predicate | transportModeAssociated |
P43050
|
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: [ZHP, transportModeAssociated, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeAssociated Context triple: [ZHP, transportModeAssociated, rail]
-
A.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
B.
hasTransportationRelation
chosen
Indicates a relationship in which one entity provides, uses, is connected by, or is otherwise associated with a means or mode of transportation to another entity or location.
-
C.
transportModeIntegration
Indicates that different modes of transportation are coordinated or combined to enable seamless or efficient movement within a journey or transport system.
-
D.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
E.
transportDependency
Indicates that one entity’s ability to be transported or to function in transport depends on another entity or transport resource.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91abc1008190a19de4f8f0112c9d |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.