Triple
T34159177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia–Europe |
E876225
|
entity |
| Predicate | usesMaritimePassage |
P144789
|
FINISHED |
| Object | Suez Canal |
—
|
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: Suez Canal | Statement: [Asia–Europe, usesMaritimePassage, Suez Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMaritimePassage Context triple: [Asia–Europe, usesMaritimePassage, Suez Canal]
-
A.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
-
B.
isMajorMarinePassage
chosen
Indicates that a waterway serves as a primary route for significant marine or ocean-going vessel traffic.
-
C.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
D.
hasMaritimeZone
Indicates that one entity possesses or is associated with a specific maritime area or jurisdictional sea zone.
-
E.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:54 a.m.