Triple
T14816736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos, Prince of Asturias |
E348336
|
entity |
| Predicate | reignAsHeirStart |
P115841
|
FINISHED |
| Object | 1556 |
—
|
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: 1556 | Statement: [Carlos, Prince of Asturias, reignAsHeirStart, 1556]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsHeirStart Context triple: [Carlos, Prince of Asturias, reignAsHeirStart, 1556]
-
A.
reignAsHeirApparentEnd
Indicates the point in time or event at which an individual’s period of serving as heir apparent to a throne or title comes to an end.
-
B.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
reignStartAsPrinceOfAragon
Indicates the date or event when an individual began their reign holding the title of Prince of Aragon.
-
D.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
E.
reignAsRegentStart
Indicates the point in time when an individual begins exercising ruling authority as a regent on behalf of another.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe2c1ec81908b3dff7a5d0e85d0 |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:49 a.m.