Triple
T29633905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luis de Velasco y Castilla |
E755657
|
entity |
| Predicate | officeEndForViceroyOfNewSpain |
P50647
|
FINISHED |
| Object | 1595 |
—
|
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: 1595 | Statement: [Luis de Velasco y Castilla, officeEndForViceroyOfNewSpain, 1595]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeEndForViceroyOfNewSpain Context triple: [Luis de Velasco y Castilla, officeEndForViceroyOfNewSpain, 1595]
-
A.
officeStartForViceroyOfNewSpain
Indicates the date or point in time when an individual begins their term as Viceroy of New Spain.
-
B.
endTimeAsViceroyOfNewSpain
chosen
Indicates the point in time when an individual’s tenure or service as Viceroy of New Spain came to an end.
-
C.
officeEndTimeAsViceroyOfNewGranada
Indicates the date and time at which an individual’s tenure as Viceroy of New Granada ended.
-
D.
succeededByAsViceroyOfNewSpain
Indicates that one individual directly followed another in holding the position of Viceroy of New Spain.
-
E.
officeEndAsViceroyOfRíoDeLaPlata
Indicates the time or event marking when an individual’s tenure as Viceroy of the Río de la Plata comes to an end.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 28, 2026, 6:42 p.m.