Triple
T7154069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Andorra |
E166763
|
entity |
| Predicate | definesCitizenship |
P22055
|
FINISHED |
| Object | Andorran 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: Andorran citizenship | Statement: [Constitution of Andorra, definesCitizenship, Andorran citizenship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCitizenship Context triple: [Constitution of Andorra, definesCitizenship, Andorran citizenship]
-
A.
definedCitizenship
chosen
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
B.
citizenshipContext
Indicates the legal or social circumstances under which an entity holds or is granted citizenship in a particular state or jurisdiction.
-
C.
citizenshipType
Indicates the specific legal category or status of an individual's citizenship in relation to a state or country.
-
D.
countryOfCitizenship
Indicates the country in which a person or entity holds legal citizenship.
-
E.
requiresCitizenship
Indicates that one entity can only obtain, access, or participate in another entity if it holds citizenship 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f68384819095e6aef89555442a |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.