Triple
T37045210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo–Benha railway corridor |
E916886
|
entity |
| Predicate | connectsToFurtherDestination |
P77537
|
FINISHED |
| Object | Alexandria via Benha |
—
|
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: Alexandria via Benha | Statement: [Cairo–Benha railway corridor, connectsToFurtherDestination, Alexandria via Benha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToFurtherDestination Context triple: [Cairo–Benha railway corridor, connectsToFurtherDestination, Alexandria via Benha]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
continuesToward
chosen
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
C.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
D.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
E.
indirectlyConnects
Indicates that one entity is connected to another through one or more intermediate entities or links, rather than by a direct connection.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:14 p.m.