Triple
T9873987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Lankan Australian |
E240027
|
entity |
| Predicate | mayHoldCitizenship |
P36272
|
FINISHED |
| Object | Sri Lankan 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: Sri Lankan citizenship | Statement: [Sri Lankan Australian, mayHoldCitizenship, Sri Lankan citizenship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHoldCitizenship Context triple: [Sri Lankan Australian, mayHoldCitizenship, Sri Lankan citizenship]
-
A.
mayHoldCitizenshipOf
chosen
Indicates that an entity is allowed or eligible to possess citizenship status of a specified country or jurisdiction.
-
B.
mayHoldDualCitizenshipWith
Indicates that an entity is allowed to simultaneously hold citizenship in the specified other country or jurisdiction.
-
C.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
D.
laterCitizenship
Indicates that an entity acquired citizenship in a country or polity at a later point in time, after some earlier status or affiliation.
-
E.
hasTypicalCitizenship
Indicates that an entity is generally or commonly a citizen of a specified country or jurisdiction.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3f89fa081908b58956902c193cf |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:37 p.m.