Triple
T34732827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Matapan |
E1001258
|
entity |
| Predicate | seaRouteJunctionFor |
P27556
|
FINISHED |
| Object | eastern Mediterranean |
—
|
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: eastern Mediterranean | Statement: [Cape Matapan, seaRouteJunctionFor, eastern Mediterranean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaRouteJunctionFor Context triple: [Cape Matapan, seaRouteJunctionFor, eastern Mediterranean]
-
A.
marineRouteType
Indicates the specific kind or classification of a maritime route used for travel, transport, or navigation between locations.
-
B.
hasSeaRouteConnection
chosen
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
-
D.
seaRouteRole
Indicates the specific function or responsibility an entity has within a sea route, such as operating, managing, or otherwise participating in that maritime pathway.
-
E.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.