Triple
T3933300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonio José Amar y Borbón |
E90846
|
entity |
| Predicate | officeStartTimeAsViceroyOfNewGranada |
P52619
|
FINISHED |
| Object | 1803 |
—
|
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: 1803 | Statement: [Antonio José Amar y Borbón, officeStartTimeAsViceroyOfNewGranada, 1803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartTimeAsViceroyOfNewGranada Context triple: [Antonio José Amar y Borbón, officeStartTimeAsViceroyOfNewGranada, 1803]
-
A.
officeStartAsViceroyOfRíoDeLaPlata
Indicates the time or event when someone begins serving in the office of Viceroy of the Río de la Plata.
-
B.
startTimeAsViceroyOfPeru
Indicates the date and time when an individual began their tenure serving as Viceroy of Peru.
-
C.
startTimeAsViceroyOfNewSpain
Indicates the date and time when an individual began serving as Viceroy of New Spain.
-
D.
endTimeAsViceroyOfPeru
Indicates the date and time when an individual's tenure or service as Viceroy of Peru came to an end.
-
E.
endTimeAsViceroyOfNewSpain
Indicates the point in time when an individual’s tenure or service as Viceroy of New Spain came to an end.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcab1808190bf653f29062cdddb |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeed3260cc8190bf294bdab507b1f9 |
completed | March 9, 2026, 3:54 p.m. |
Created at: March 9, 2026, 3:23 p.m.