Triple
T31117415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsstädte |
E793127
|
entity |
| Predicate | typicalGovernmentInstitutions |
P86206
|
FINISHED |
| Object | city 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: city council | Statement: [Reichsstädte, typicalGovernmentInstitutions, city council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGovernmentInstitutions Context triple: [Reichsstädte, typicalGovernmentInstitutions, city council]
-
A.
governmentOffices
Indicates that one entity is a government office or administrative agency associated with, located in, or serving the other entity.
-
B.
typeOfGovernmentInstitution
chosen
Indicates that one entity is a government institution of the type or category specified by the other entity.
-
C.
governmentOffice
Indicates that an entity functions as an official administrative or governmental office responsible for carrying out public or state-related duties.
-
D.
mainGovernment
Indicates that one entity serves as the primary governing authority or central government for another entity.
-
E.
hasGovernmentInstitution
Indicates that a given entity possesses, hosts, or is served by a formal governmental body or institution.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.