Triple
T30770749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Sirte |
E783515
|
entity |
| Predicate | hasMaritimeBoundaryDisputeWith |
P169531
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Gulf of Sirte, hasMaritimeBoundaryDisputeWith, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeBoundaryDisputeWith Context triple: [Gulf of Sirte, hasMaritimeBoundaryDisputeWith, United States]
-
A.
hasDisputedMaritimeBoundary
chosen
Indicates that there is an unresolved or contested maritime boundary claim between two or more entities.
-
B.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
C.
hasTerritorialSeaIn
Indicates that an entity’s territorial sea is located within or extends into the area or jurisdiction of another entity.
-
D.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
E.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
- 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_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: April 29, 2026, 8:40 p.m.