Triple
T37693368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Overseas citizenship |
E938864
|
entity |
| Predicate | loss |
P43002
|
FINISHED |
| Object | possible by 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: possible by voluntary renunciation | Statement: [British Overseas citizenship, loss, possible by voluntary renunciation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loss Context triple: [British Overseas citizenship, loss, possible by voluntary renunciation]
-
A.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
B.
losses
Indicates that an entity experiences a decrease in value, quantity, or advantage as a result of some event or comparison.
-
C.
lossType
chosen
Indicates the specific category or nature of a loss associated with an entity or event.
-
D.
lostDuring
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
E.
lossContext
Indicates that some relevant information, state, or conditions from an earlier point in a process or interaction are no longer available or preserved in the current context.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.