Triple
T32380953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greene County Commission |
E827413
|
entity |
| Predicate | holdsPublicMeetings |
P86237
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Greene County Commission, holdsPublicMeetings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsPublicMeetings Context triple: [Greene County Commission, holdsPublicMeetings, true]
-
A.
hasPublicMeetings
chosen
Indicates that an entity organizes or holds meetings that are open and accessible to the general public.
-
B.
allowsPublicHearings
Indicates that an entity permits public hearings to be held, allowing members of the public to attend and/or participate.
-
C.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
D.
hasGeneralAssembly
Indicates that an entity possesses or is associated with a general assembly as its formal deliberative or decision-making body.
-
E.
hasPlenarySessions
Indicates that an event or organization includes formal plenary sessions as part of its activities or structure.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.