Triple
T15248769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Township Council–Manager |
E364458
|
entity |
| Predicate | managerImplements |
P70127
|
FINISHED |
| Object | ordinances and resolutions of 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: ordinances and resolutions of council | Statement: [Township Council–Manager, managerImplements, ordinances and resolutions of council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerImplements Context triple: [Township Council–Manager, managerImplements, ordinances and resolutions of council]
-
A.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
B.
managerType
Indicates the specific category or role classification of a manager within an organizational or system context.
-
C.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
D.
managementController
Indicates that one entity serves as the management controller responsible for overseeing, configuring, or administering another entity.
-
E.
areImplementedBy
chosen
Indicates that one entity serves as the concrete realization or execution of the specification, design, or interface defined by 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_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.