Triple
T15248766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Township Council–Manager |
E364458
|
entity |
| Predicate | mayorRoleTypically |
P117769
|
FINISHED |
| Object | largely ceremonial |
—
|
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: largely ceremonial | Statement: [Township Council–Manager, mayorRoleTypically, largely ceremonial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayorRoleTypically Context triple: [Township Council–Manager, mayorRoleTypically, largely ceremonial]
-
A.
mayorType
Indicates the specific category or role classification of a mayor in relation to their office or jurisdiction.
-
B.
mayorAppointment
Indicates that one entity appoints or designates another entity to serve in the role of mayor.
-
C.
mayorSelection
Indicates the process or outcome of choosing or appointing someone to serve as mayor of a place.
-
D.
hasMayor
Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
-
E.
hasMayorOffice
Indicates that a particular entity serves as the office or official position held by a mayor of another entity.
- F. None of above. chosen
Provenance (4 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_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.