Triple
T15637315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Niue |
E375978
|
entity |
| Predicate | allowsPoliticalParties |
P70061
|
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, allowsPoliticalParties, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPoliticalParties Context triple: [government of Niue, allowsPoliticalParties, yes]
-
A.
eligibleParties
Indicates that certain entities are qualified or permitted to participate in, benefit from, or be subject to a specified agreement, process, or condition.
-
B.
politicalPartiesAllowed
chosen
Indicates whether the formation and operation of political parties is legally permitted within a given political system or jurisdiction.
-
C.
hasPoliticalParties
Indicates that a political system, country, or region includes one or more organized political parties operating within it.
-
D.
includesPoliticalPartiesFrom
Indicates that a collection, group, or context contains or encompasses one or more political parties originating from a specified source or jurisdiction.
-
E.
ledPoliticalParty
Indicates that one entity served as the leader or head of a particular political party.
- 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.