Triple
T31589211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Eilat |
E806042
|
entity |
| Predicate | providesDirectAccessTo |
P51771
|
FINISHED |
| Object | Indian Ocean |
—
|
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: Indian Ocean | Statement: [Port of Eilat, providesDirectAccessTo, Indian Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesDirectAccessTo Context triple: [Port of Eilat, providesDirectAccessTo, Indian Ocean]
-
A.
accessProvides
chosen
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
B.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
E.
assumesAccessTo
Indicates that one entity presupposes or takes for granted that it has access to another entity, resource, or piece of information.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 30, 2026, 10:27 p.m.