Triple
T21067132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carloman II |
E519005
|
entity |
| Predicate | ruledAsSoleKingStart |
P142719
|
FINISHED |
| Object | 882 |
—
|
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: 882 | Statement: [Carloman II, ruledAsSoleKingStart, 882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledAsSoleKingStart Context triple: [Carloman II, ruledAsSoleKingStart, 882]
-
A.
reignAsCoRulerStart
Indicates the time or event when an entity begins to exercise ruling authority jointly with one or more other rulers.
-
B.
reignStartAsKingOfBohemia
Indicates the date or event marking when an individual began their reign as King of Bohemia.
-
C.
ascendedToThroneAs
Indicates that an individual assumed royal power and officially became the reigning monarch under a specific title or role.
-
D.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
E.
reignStartAsKingOfEastFrancia
Indicates the date or event when an individual began their reign as king of East Francia.
- F. None of above. chosen
Provenance (4 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb455fc81909cc63fa0e87b6a35 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:45 p.m.