Triple
T6977362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bismarck |
E161746
|
entity |
| Predicate | hasCityGovernmentType |
P73614
|
FINISHED |
| Object | commission system |
—
|
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: commission system | Statement: [Bismarck, hasCityGovernmentType, commission system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityGovernmentType Context triple: [Bismarck, hasCityGovernmentType, commission system]
-
A.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
B.
hasGovernmentSeatType
Indicates the specific type or classification of the location where a government’s central authority or administrative seat is situated.
-
C.
cityGovernment
Indicates that a city’s governing authority has jurisdiction, control, or administrative responsibility over the referenced entity.
-
D.
hasLocalGovernmentBody
Indicates that an entity is administered or overseen by a specific local government authority or governing body.
-
E.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db677bbc8190a084b6951e5c3182 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8e2d7b48190b37bb13984663cde |
completed | March 27, 2026, 7:22 p.m. |
Created at: March 27, 2026, 2:31 p.m.