Triple
T4651353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig III of Bavaria |
E102300
|
entity |
| Predicate | dateOfCoronation |
P1508
|
FINISHED |
| Object | 1913-11-08 |
—
|
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: 1913-11-08 | Statement: [Ludwig III of Bavaria, dateOfCoronation, 1913-11-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfCoronation Context triple: [Ludwig III of Bavaria, dateOfCoronation, 1913-11-08]
-
A.
coronationDate
chosen
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
B.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
C.
coronationAsCoEmperorDate
Indicates the date on which an individual was formally crowned or installed as a co-emperor alongside another reigning emperor.
-
D.
firstCoronationHeldFor
Indicates that a particular entity was the subject or beneficiary of the first coronation event associated with another entity.
-
E.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.