Triple
T1378978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo–Damietta line |
E29292
|
entity |
| Predicate | passengerRole |
P15253
|
FINISHED |
| Object | intercity connection |
—
|
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: intercity connection | Statement: [Cairo–Damietta line, passengerRole, intercity connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerRole Context triple: [Cairo–Damietta line, passengerRole, intercity connection]
-
A.
hasPassengerRole
chosen
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
B.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
C.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
D.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
E.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3187f248190a5813274b0ef944d |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.