Triple
T35934269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rural Municipality of Glen Bain No. 105 |
E1039251
|
entity |
| Predicate | hasCouncilMeetingFrequency |
P2557
|
FINISHED |
| Object | monthly |
—
|
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: monthly | Statement: [Rural Municipality of Glen Bain No. 105, hasCouncilMeetingFrequency, monthly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouncilMeetingFrequency Context triple: [Rural Municipality of Glen Bain No. 105, hasCouncilMeetingFrequency, monthly]
-
A.
frequencyOfMinisterialMeetings
Indicates how often ministerial-level meetings occur within a given period or context.
-
B.
hasPublicMeetings
Indicates that an entity organizes or holds meetings that are open and accessible to the general public.
-
C.
securityCouncilMandateRenewalFrequency
Indicates how often a United Nations Security Council mandate is renewed or extended over time.
-
D.
meetingFrequency
chosen
Indicates how often a meeting or recurring gathering takes place over a given period.
-
E.
councilHeldHere
Indicates that a council or formal assembly took place at the specified 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.