Triple
T14816737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos, Prince of Asturias |
E348336
|
entity |
| Predicate | reignAsHeirEnd |
P71884
|
FINISHED |
| Object | 1568 |
—
|
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: 1568 | Statement: [Carlos, Prince of Asturias, reignAsHeirEnd, 1568]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsHeirEnd Context triple: [Carlos, Prince of Asturias, reignAsHeirEnd, 1568]
-
A.
reignAsHeirApparentEnd
chosen
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.
reignAsKingEnd
Indicates the point in time or event at which an entity’s period of reigning as king comes to an end.
-
C.
reignAsPrinceEnd
Indicates the point in time or event at which an individual’s tenure or role as a prince comes to an end.
-
D.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
-
E.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
- 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_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. |
Created at: April 10, 2026, 1:49 a.m.