Triple
T5954658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandria City Council |
E132481
|
entity |
| Predicate | partOfGovernmentType |
P13419
|
FINISHED |
| Object | council–manager government |
—
|
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: council–manager government | Statement: [Alexandria City Council, partOfGovernmentType, council–manager government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfGovernmentType Context triple: [Alexandria City Council, partOfGovernmentType, council–manager government]
-
A.
isPartOfGovernment
chosen
Indicates that an entity belongs to, is included within, or functions as a component of a governmental body or system.
-
B.
typeOfMinistry
Indicates the specific category or kind of ministry that an entity belongs to or represents.
-
C.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
D.
governmentBodyType
Indicates the classification or category of a governmental organization based on its structural or functional role.
-
E.
governmentBranch
Indicates that one entity functions as an official division or branch within the structure of a government.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.