Triple
T29864001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizpe, Sonora |
E758398
|
entity |
| Predicate | previousInhabitants |
P3032
|
FINISHED |
| Object | Ópata people |
E1288903
|
NE 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: Ópata people | Statement: [Arizpe, Sonora, previousInhabitants, Ópata people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousInhabitants Context triple: [Arizpe, Sonora, previousInhabitants, Ópata people]
-
A.
historicallyInhabitedBy
chosen
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
B.
formerPopulation
Indicates that an entity once had a certain population value or size during a past time period but no longer does.
-
C.
originalInhabitant
Indicates that an entity was among the first or earliest residents of a particular place or territory.
-
D.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
E.
predecessorPopulation
Indicates that one population entity is the immediate prior version or state of another population entity in a temporal or evolutionary sequence.
- F. None of above.
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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34665207a081908152ee52b113938a |
completed | June 18, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 29, 2026, 5:50 p.m.