Triple
T15637321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Niue |
E375978
|
entity |
| Predicate | canEnterTreaties |
P11785
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [government of Niue, canEnterTreaties, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEnterTreaties Context triple: [government of Niue, canEnterTreaties, yes]
-
A.
hasTreatyRight
Indicates that an entity holds a legally recognized right or entitlement established by a formal treaty with another party.
-
B.
treatyPower
chosen
Indicates that one entity holds the authority or capacity to negotiate, conclude, or be bound by treaties with another entity.
-
C.
hasMainTreaty
Indicates that one entity is the primary or principal treaty associated with another entity.
-
D.
roleInTreaties
Indicates the specific capacity, function, or position an entity holds within the context of one or more treaties.
-
E.
treatyStatus
Indicates the current legal or diplomatic condition of a treaty between parties, such as whether it is proposed, signed, ratified, active, suspended, or terminated.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.