Triple
T11998042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambayong |
E285579
|
entity |
| Predicate | hasLocalElections |
P22629
|
FINISHED |
| Object | every 3 years |
—
|
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: every 3 years | Statement: [Lambayong, hasLocalElections, every 3 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalElections Context triple: [Lambayong, hasLocalElections, every 3 years]
-
A.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
B.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
-
C.
hasByElections
Indicates that one entity conducts, experiences, or is associated with one or more by-elections in relation to another contextual entity (such as a jurisdiction, office, or time period).
-
D.
hasRegularElections
chosen
Indicates that a governing body or political entity holds elections at consistent, scheduled intervals according to established rules or norms.
-
E.
electionHeldIn
Indicates that an election event took place within a specific geographic or political location.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c172788190b92042e9d10a48bf |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.