Triple
T27711506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British people |
E698702
|
entity |
| Predicate | usesCitizenship |
P98308
|
FINISHED |
| Object | British citizen |
—
|
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: British citizen | Statement: [British people, usesCitizenship, British citizen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCitizenship Context triple: [British people, usesCitizenship, British citizen]
-
A.
hasTypicalCitizenship
Indicates that an entity is generally or commonly a citizen of a specified country or jurisdiction.
-
B.
requiresCitizenship
Indicates that one entity can only obtain, access, or participate in another entity if it holds citizenship of a specified country or jurisdiction.
-
C.
isCitizenOf
chosen
Indicates that a person holds legal nationality or citizenship status in a particular country or state.
-
D.
usedByCountryOfCitizenship
Indicates that something is utilized or employed by the country in which a person (or group of people) holds citizenship.
-
E.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 3:02 p.m.