Triple
T10591575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carol I of Romania |
E250001
|
entity |
| Predicate | dateBecameDomnitor |
P47970
|
FINISHED |
| Object | 1866-05-10 |
—
|
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: 1866-05-10 | Statement: [Carol I of Romania, dateBecameDomnitor, 1866-05-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateBecameDomnitor Context triple: [Carol I of Romania, dateBecameDomnitor, 1866-05-10]
-
A.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
B.
reignAsGrandDukeOfLithuaniaStart
Indicates the time at which an individual begins their tenure as Grand Duke of Lithuania.
-
C.
reignAsGrandPrinceOfMoscowFrom
Indicates that a person held the position of Grand Prince of Moscow starting from a specified time.
-
D.
placedOnThrone
Indicates that an entity is formally elevated to a position of rulership or authority, typically by being seated on a throne.
-
E.
dateOfSuccession
chosen
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277c79808190acc872919eadd126 |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.