Triple
T33091582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niuean passports |
E846795
|
entity |
| Predicate | hasHolderRight |
P193612
|
FINISHED |
| Object | consular assistance subject to Niue’s arrangements |
—
|
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: consular assistance subject to Niue’s arrangements | Statement: [Niuean passports, hasHolderRight, consular assistance subject to Niue’s arrangements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHolderRight Context triple: [Niuean passports, hasHolderRight, consular assistance subject to Niue’s arrangements]
-
A.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
B.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
C.
hasHolding
Indicates that one entity possesses, controls, or maintains ownership or custody of another entity as an asset or item.
-
D.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control of another entity.
-
E.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: May 1, 2026, 1:26 a.m.