Triple
T25795062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 16 April 1871 |
E649657
|
entity |
| Predicate | definedOffice |
P84375
|
FINISHED |
| Object | Reichskanzler |
—
|
NE NERFINISHED |
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: Reichskanzler | Statement: [Constitution of 16 April 1871, definedOffice, Reichskanzler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedOffice Context triple: [Constitution of 16 April 1871, definedOffice, Reichskanzler]
-
A.
definesOfficeOf
chosen
Indicates that one entity specifies or establishes the official role, position, or office associated with another entity.
-
B.
identifiesOffice
Indicates that one entity serves to specify or recognize the particular office or official position associated with another entity.
-
C.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
-
D.
denotesOfficeIn
Indicates that an entity holds or maintains an official office or branch located within a specified place or jurisdiction.
-
E.
specifiesOffice
Indicates that an entity is assigned to or associated with a particular office or official position.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 6:28 a.m.