Triple
T15248750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Township Council–Manager |
E364458
|
entity |
| Predicate | managerAppointedBy |
P257
|
FINISHED |
| Object | township council |
—
|
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: township council | Statement: [Township Council–Manager, managerAppointedBy, township council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerAppointedBy Context triple: [Township Council–Manager, managerAppointedBy, township council]
-
A.
appointedFrom
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
B.
appointedBy
chosen
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
-
C.
representativeAppointedBy
Indicates that one entity serves as a representative who has been formally designated or appointed by another entity.
-
D.
appointedIn
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
-
E.
appointedAs
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f62b9c8190b9ad40e2d1912b63 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.