Triple
T28315003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | March of Brandenburg |
E714109
|
entity |
| Predicate | rulerTitleLater |
P112121
|
FINISHED |
| Object | Prince-elector of Brandenburg |
—
|
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: Prince-elector of Brandenburg | Statement: [March of Brandenburg, rulerTitleLater, Prince-elector of Brandenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulerTitleLater Context triple: [March of Brandenburg, rulerTitleLater, Prince-elector of Brandenburg]
-
A.
laterRulerTitle
chosen
Indicates that an entity held a particular ruler title at a later point in time, after some earlier status or title.
-
B.
titleHolderRuled
Indicates that the entity holding a particular title exercised ruling authority or governance over another entity or domain.
-
C.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
D.
hasRulerTitle
Indicates that a ruler holds or is associated with a specific formal title of rulership.
-
E.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644e5e3c8819092a5295a8c566930 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:42 p.m.