Triple
T24089463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh HaNikra |
E596746
|
entity |
| Predicate | railwayLineConnected |
P848
|
FINISHED |
| Object | Haifa–Beirut–Tripoli railway |
—
|
NE NERFINISHED |
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: Haifa–Beirut–Tripoli railway | Statement: [Rosh HaNikra, railwayLineConnected, Haifa–Beirut–Tripoli railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineConnected Context triple: [Rosh HaNikra, railwayLineConnected, Haifa–Beirut–Tripoli railway]
-
A.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
railwayLineNow
Indicates that a previously existing railway line has been replaced, succeeded, or is currently represented by a new or different railway line.
-
E.
connectsToRailwayNetwork
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2d405881909469aa95901ab87b |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:48 p.m.