Triple
T32609960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian South Africans |
E833626
|
entity |
| Predicate | dualCitizenshipPotential |
P23321
|
FINISHED |
| Object | Italian citizenship |
—
|
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: Italian citizenship | Statement: [Italian South Africans, dualCitizenshipPotential, Italian citizenship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dualCitizenshipPotential Context triple: [Italian South Africans, dualCitizenshipPotential, Italian citizenship]
-
A.
hasDualCitizenship
Indicates that a person is legally recognized as a citizen of two different countries at the same time.
-
B.
dualCitizenshipStatus
Indicates that an entity holds legal citizenship in two different countries simultaneously.
-
C.
mayHoldDualCitizenshipWith
chosen
Indicates that an entity is allowed to simultaneously hold citizenship in the specified other country or jurisdiction.
-
D.
mayHoldCitizenshipOf
Indicates that an entity is allowed or eligible to possess citizenship status of a specified country or jurisdiction.
-
E.
possibleCountryOfCitizenship
Indicates that an entity could plausibly be a country in which the person or agent may hold, or be eligible to hold, citizenship.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.