Triple
T26402334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Magdeburg |
E663734
|
entity |
| Predicate | titleHolderAlsoHeld |
P177098
|
FINISHED |
| Object | Elector of Brandenburg |
—
|
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: Elector of Brandenburg | Statement: [Duke of Magdeburg, titleHolderAlsoHeld, Elector of Brandenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderAlsoHeld Context triple: [Duke of Magdeburg, titleHolderAlsoHeld, Elector of Brandenburg]
-
A.
titleHeldAlso
chosen
Indicates that an entity holds an additional title concurrently with another title or role.
-
B.
titleHolderWas
Indicates that an entity previously held a specific title or position before it passed to someone or something else.
-
C.
titleHolderCouldBe
Indicates that a particular entity is a possible or potential holder of a specified title or position.
-
D.
titleHeldConcurrentlyWith
Indicates that one title or position was held at the same time as another title or position by the same entity.
-
E.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 11:32 p.m.