Triple
T28384820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand citizenship |
E718991
|
entity |
| Predicate | mayBeLostBy |
P82574
|
FINISHED |
| Object | voluntary renunciation |
—
|
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: voluntary renunciation | Statement: [New Zealand citizenship, mayBeLostBy, voluntary renunciation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeLostBy Context triple: [New Zealand citizenship, mayBeLostBy, voluntary renunciation]
-
A.
canBeLostBy
chosen
Indicates that something is capable of being lost or forfeited by a particular entity.
-
B.
canBeLostThrough
Indicates that something is capable of being lost, removed, or forfeited as a result of a specified process, action, or condition.
-
C.
isLostBy
Indicates that something ceases to be possessed, controlled, or retained by a particular entity.
-
D.
canBeBlockedWhenLost
Indicates that an item, once lost, is capable of being deactivated or blocked to prevent further use or access.
-
E.
lostOrDestroyed
Indicates that something has ceased to exist in its original, usable form, either by being misplaced beyond recovery or physically destroyed.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 1:09 a.m.