Triple
T546936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch-chancellor of the Holy Roman Empire |
E12752
|
entity |
| Predicate | hasComponentOffice |
P11900
|
FINISHED |
| Object | Arch-chancellor of Germany |
—
|
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: Arch-chancellor of Germany | Statement: [Arch-chancellor of the Holy Roman Empire, hasComponentOffice, Arch-chancellor of Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentOffice Context triple: [Arch-chancellor of the Holy Roman Empire, hasComponentOffice, Arch-chancellor of Germany]
-
A.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
B.
hasOfficeType
Indicates that an entity’s office is classified as a specific type or category of office.
-
C.
includedOffice
chosen
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
D.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
-
E.
hasPositionInOrganization
Indicates that an entity holds a specific role, job, or position within a particular organization.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e2e8c88190a66d759ed3094e18 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.