Triple
T38202453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popé’s Rebellion |
E1009103
|
entity |
| Predicate | spanishReturn |
P190286
|
FINISHED |
| Object | Spanish reconquest of New Mexico in 1692 |
—
|
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: Spanish reconquest of New Mexico in 1692 | Statement: [Popé’s Rebellion, spanishReturn, Spanish reconquest of New Mexico in 1692]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spanishReturn Context triple: [Popé’s Rebellion, spanishReturn, Spanish reconquest of New Mexico in 1692]
-
A.
SpanishEditionURL
Indicates the web address where the Spanish-language edition or version of something can be accessed.
-
B.
returnToSpain
Indicates that an entity goes back to Spain, typically after having been away.
-
C.
SpanishObjective
Indicates that an entity is the target or goal of an action, relation, or expression specifically in the Spanish language.
-
D.
spanishVersionUsage
Indicates how and in what context the Spanish-language version of something is used.
-
E.
SPAN-E
Indicates a relationship where one entity extends over, covers, or bridges across another entity or a specified interval in space, time, or sequence.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:30 p.m.