Triple
T2739818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacuba |
E60721
|
entity |
| Predicate | hasPreHispanicOrigin |
P26706
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tacuba, hasPreHispanicOrigin, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreHispanicOrigin Context triple: [Tacuba, hasPreHispanicOrigin, yes]
-
A.
preHispanicUse
Indicates that something was used or practiced during the pre-Hispanic period, before Spanish contact or colonization.
-
B.
hasIndigenousHistory
chosen
Indicates that an entity is associated with, influenced by, or located in a place or context that has a documented or recognized history of Indigenous peoples, cultures, or presence.
-
C.
hasSignificantSpanishInfluence
Indicates that one entity has been strongly shaped or notably affected by Spanish culture, language, practices, or presence.
-
D.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
E.
hasIndigenousPresence
Indicates that an indigenous community, culture, or population is present, active, or historically rooted in the referenced place or context.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb2da94c8190bc9d23262e3dfc07 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.