Triple
T7334669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Bonte |
E169095
|
entity |
| Predicate | levelOfGovernmentServed |
P1085
|
FINISHED |
| Object | local |
—
|
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: local | Statement: [Hans Bonte, levelOfGovernmentServed, local]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelOfGovernmentServed Context triple: [Hans Bonte, levelOfGovernmentServed, local]
-
A.
servesLevelOfGovernment
Indicates that one entity performs duties or functions on behalf of, or under the authority of, a specified level of government (e.g., local, regional, national).
-
B.
levelOfGovernment
chosen
Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
-
C.
governmentServed
Indicates that a person has held a position serving in or working for a particular government.
-
D.
governmentTypeServed
Indicates the type of government that an entity serves, is affiliated with, or operates under in its role or function.
-
E.
governmentBodyServed
Indicates that one entity has served in an official capacity within, or as a member of, a particular government body.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.