Triple
T14927232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regency of Cardinal Henry of Portugal |
E372163
|
entity |
| Predicate | regentBirthDate |
P116695
|
FINISHED |
| Object | 1512 |
—
|
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: 1512 | Statement: [Regency of Cardinal Henry of Portugal, regentBirthDate, 1512]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regentBirthDate Context triple: [Regency of Cardinal Henry of Portugal, regentBirthDate, 1512]
-
A.
currentMonarchBirthDate
Indicates the date on which the person who is the current monarch of a specified realm was born.
-
B.
dateOfBirthOfChildRoyalReign
Indicates the specific date on which a child was born during a particular royal’s reign.
-
C.
dateOfRoyalBaptism
Indicates the date on which a royal individual underwent their official baptism ceremony.
-
D.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
-
E.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded633da0c8190b39f606212e48e71 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:35 a.m.