Triple
T2957310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taracahitic |
E79962
|
entity |
| Predicate | spokenInThePastBy |
P23402
|
FINISHED |
| Object | indigenous peoples of northwestern Mexico |
—
|
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: indigenous peoples of northwestern Mexico | Statement: [Taracahitic, spokenInThePastBy, indigenous peoples of northwestern Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenInThePastBy Context triple: [Taracahitic, spokenInThePastBy, indigenous peoples of northwestern Mexico]
-
A.
spokenBefore
Indicates that one entity has spoken or produced speech earlier in time than another entity.
-
B.
historicallySpoke
chosen
Indicates that an entity used a particular language as a spoken language during some period in the past.
-
C.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
-
D.
spokenBy
Indicates that a particular utterance, statement, or piece of speech is produced or said by a specific entity.
-
E.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992b33e081909d22a19d5064c47d |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.