Triple
T15432079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luis de Velasco |
E369664
|
entity |
| Predicate | appointedAsViceroyOfNewSpain |
P118753
|
FINISHED |
| Object | 1550 |
—
|
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: 1550 | Statement: [Luis de Velasco, appointedAsViceroyOfNewSpain, 1550]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsViceroyOfNewSpain Context triple: [Luis de Velasco, appointedAsViceroyOfNewSpain, 1550]
-
A.
succeededByAsViceroyOfNewSpain
Indicates that one individual directly followed another in holding the position of Viceroy of New Spain.
-
B.
precededByAsViceroyOfNewSpain
Indicates that one entity previously served as Viceroy of New Spain immediately before another entity in the line of succession.
-
C.
startTimeAsViceroyOfNewSpain
Indicates the date and time when an individual began serving as Viceroy of New Spain.
-
D.
succeededByAsViceroyOfPeru
Indicates that one person directly followed another in holding the position of Viceroy of Peru.
-
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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eda01cc8190843e23b260b8503c |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.