Triple
T29924317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Snake Island had limited effect on maritime delimitation" |
E760036
|
entity |
| Predicate | limitsClaimOf |
P168266
|
FINISHED |
| Object | Ukraine |
—
|
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: Ukraine | Statement: ["Snake Island had limited effect on maritime delimitation", limitsClaimOf, Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitsClaimOf Context triple: ["Snake Island had limited effect on maritime delimitation", limitsClaimOf, Ukraine]
-
A.
claim1
Indicates that an entity asserts, alleges, or maintains the truth of a particular statement, proposition, or fact.
-
B.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
C.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
D.
modalClaim
Indicates that the statement is being made with a modal qualification, such as possibility, necessity, or obligation, rather than as an unqualified factual claim.
-
E.
capitalClaimed
Indicates that an entity asserts or designates another entity as its capital.
- F. None of above. chosen
Provenance (4 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67795fdd4819088f3c7d0de598699 |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:15 p.m.