Triple
T30770791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Sidra incident 1981 |
E783516
|
entity |
| Predicate | USPositionOnWaters |
P1489
|
FINISHED |
| Object | international waters |
—
|
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: international waters | Statement: [Gulf of Sidra incident 1981, USPositionOnWaters, international waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USPositionOnWaters Context triple: [Gulf of Sidra incident 1981, USPositionOnWaters, international waters]
-
A.
oceanLocation
Indicates that one entity is geographically located in, on, or adjacent to a particular ocean.
-
B.
locatedOnWaterbody
chosen
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
C.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
D.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
-
E.
positionRelativeToSurfaceCurrents
Indicates the spatial relationship of an entity’s location or movement with respect to the direction and pattern of surface currents.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fc1913081909b621a90cb555115 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.