Triple
T35433753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Provostry of Berchtesgaden |
E1024139
|
entity |
| Predicate | laterSuccessor |
P49035
|
FINISHED |
| Object | Kingdom of Bavaria |
—
|
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: Kingdom of Bavaria | Statement: [Prince-Provostry of Berchtesgaden, laterSuccessor, Kingdom of Bavaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSuccessor Context triple: [Prince-Provostry of Berchtesgaden, laterSuccessor, Kingdom of Bavaria]
-
A.
laterAdministrativeSuccessor
chosen
Indicates that one administrative entity succeeds another in governing authority or jurisdiction at a later time.
-
B.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
C.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
E.
successorFrom
Indicates that one entity directly follows or comes after another in an ordered sequence or progression.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 3, 2026, 4:04 p.m.