Triple
T16206614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Council of Stem |
E393343
|
entity |
| Predicate | hasOfficialMeetings |
P86237
|
FINISHED |
| Object | public council meetings |
—
|
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: public council meetings | Statement: [Town Council of Stem, hasOfficialMeetings, public council meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialMeetings Context triple: [Town Council of Stem, hasOfficialMeetings, public council meetings]
-
A.
hasPublicMeetings
chosen
Indicates that an entity organizes or holds meetings that are open and accessible to the general public.
-
B.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
-
C.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
-
D.
meetingsWere
Indicates that one or more meetings occurred or were held between the referenced entities.
-
E.
hasOfficialEvents
Indicates that an entity organizes, hosts, or is associated with formally recognized or sanctioned events.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227101a3c819095ef40e50bf66433 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.