Triple
T25716428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co-Principality of Andorra |
E644874
|
entity |
| Predicate | nationalParliamentType |
P6051
|
FINISHED |
| Object | unicameral |
—
|
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: unicameral | Statement: [Co-Principality of Andorra, nationalParliamentType, unicameral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalParliamentType Context triple: [Co-Principality of Andorra, nationalParliamentType, unicameral]
-
A.
parliamentaryHouse
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
-
B.
parliamentaryGroupType
Indicates the specific kind or category of parliamentary group to which an entity belongs.
-
C.
typeOfParliamentaryBody
chosen
Indicates the specific kind or classification of a parliamentary body that an entity represents (e.g., lower house, upper house, unicameral chamber).
-
D.
legislativeChamberLevel
Indicates the hierarchical level (e.g., national, state, local) at which a legislative chamber operates within a political or governmental system.
-
E.
parliamentName
Indicates the official name assigned to a particular parliament.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 21, 2026, 9:43 p.m.