Triple
T16466475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch Daniel of Romania |
E399945
|
entity |
| Predicate | dateOfEnthronement |
P1508
|
FINISHED |
| Object | 2007-09-30 |
—
|
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: 2007-09-30 | Statement: [Patriarch Daniel of Romania, dateOfEnthronement, 2007-09-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfEnthronement Context triple: [Patriarch Daniel of Romania, dateOfEnthronement, 2007-09-30]
-
A.
ascendedToThroneIn
Indicates the time or place at which a person formally became the ruling monarch or assumed the throne.
-
B.
placedOnThrone
Indicates that an entity is formally elevated to a position of rulership or authority, typically by being seated on a throne.
-
C.
coronationDate
chosen
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
D.
dateOfSuccession
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
-
E.
ascendedToThroneAs
Indicates that an individual assumed royal power and officially became the reigning monarch under a specific title or role.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dcc52f88190958b408e49cfb512 |
completed | April 18, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.