Triple
T11032818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faulkner Act council–manager |
E260799
|
entity |
| Predicate | selectionOfCouncil |
P21035
|
FINISHED |
| Object | elected by voters |
—
|
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: elected by voters | Statement: [Faulkner Act council–manager, selectionOfCouncil, elected by voters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionOfCouncil Context triple: [Faulkner Act council–manager, selectionOfCouncil, elected by voters]
-
A.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
-
B.
councilType
chosen
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
-
C.
positionOnCouncils
Indicates that an entity holds a seat or role as a member on one or more councils.
-
D.
viewOfCouncils
Indicates that one entity holds a particular perspective, opinion, or stance regarding councils or council-related matters.
-
E.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.