Triple
T18042806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isle of Man passports |
E431691
|
entity |
| Predicate | citizenshipRequired |
P40423
|
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: [Isle of Man passports, citizenshipRequired, British citizen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citizenshipRequired Context triple: [Isle of Man passports, citizenshipRequired, British citizen]
-
A.
requiresCitizenship
chosen
Indicates that one entity can only obtain, access, or participate in another entity if it holds citizenship of a specified country or jurisdiction.
-
B.
hasCitizenshipRestriction
Indicates that there is a legal or policy-based limitation on who can obtain or hold citizenship in a given context.
-
C.
hasTypicalCitizenship
Indicates that an entity is generally or commonly a citizen of a specified country or jurisdiction.
-
D.
naturalisationRequirement
Indicates the conditions or criteria that must be met for an individual to acquire citizenship through naturalisation.
-
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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bfef454c8190ad3787502f2bdd34 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.