Triple
T11662322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar Constitution Order 2006 |
E277152
|
entity |
| Predicate | setsNumberOfElectedMembers |
P31812
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [Gibraltar Constitution Order 2006, setsNumberOfElectedMembers, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsNumberOfElectedMembers Context triple: [Gibraltar Constitution Order 2006, setsNumberOfElectedMembers, 17]
-
A.
hasElectedMembers
Indicates that an entity possesses members who have attained their positions through an election process.
-
B.
numberOfElectedMembers
chosen
Indicates the total count of individuals who have been formally chosen through an election to serve as members of a given body or group.
-
C.
numberOfAppointedMembers
Indicates the specific count of members who have been formally appointed to a group, body, or position.
-
D.
membersAreElectedIn
Indicates that the members of a group or body attain their positions through an election process held within a specified context or jurisdiction.
-
E.
hasNumberOfVotingMembers
Indicates the specific count of individuals who hold voting rights within a given group or body.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d29fdc8190af46b6e2badb1df5 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.