Triple
T16313069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLEN |
E396104
|
entity |
| Predicate | hasVotingRightsAttached |
P116569
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GLEN, hasVotingRightsAttached, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingRightsAttached Context triple: [GLEN, hasVotingRightsAttached, yes]
-
A.
hasVotingRightsClass
chosen
Indicates that an entity is associated with a specific class or category of voting rights.
-
B.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
C.
hasRelativeVotingPower
Indicates that one entity possesses a specified level or proportion of voting power relative to another entity or group.
-
D.
hasVotingMembers
Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
-
E.
hasDifferentVotingRightsFrom
Indicates that two entities possess voting rights that are not identical in terms of scope, weight, or conditions.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288dc30f48190b508220429b66e92 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.