Triple
T16988318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riga City Council |
E412126
|
entity |
| Predicate | hasElectedRole |
P111087
|
FINISHED |
| Object | Chairman of the Riga City Council |
—
|
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: Chairman of the Riga City Council | Statement: [Riga City Council, hasElectedRole, Chairman of the Riga City Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectedRole Context triple: [Riga City Council, hasElectedRole, Chairman of the Riga City Council]
-
A.
hasPrimaryElectionRole
Indicates that an entity holds a main or leading role in conducting, overseeing, or participating in a primary election.
-
B.
hasConsistentlyElected
Indicates that one entity has regularly and repeatedly chosen or voted for another entity over an extended period or across multiple selection events.
-
C.
hasProposedRole
Indicates that one entity has suggested or put forward a specific role or position for another entity.
-
D.
hasElectedLeadership
chosen
Indicates that an entity possesses leaders who have been chosen through an election or voting process.
-
E.
hasElectedMembers
Indicates that an entity possesses members who have attained their positions through an election process.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27cd2048190800a60ae653e11e1 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.