Triple
T4228084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tepehuan |
E94508
|
entity |
| Predicate | Tepehuan Revolt |
P32443
|
FINISHED |
| Object | occurred in early 17th century |
—
|
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: occurred in early 17th century | Statement: [Tepehuan, Tepehuan Revolt, occurred in early 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tepehuan Revolt Context triple: [Tepehuan, Tepehuan Revolt, occurred in early 17th century]
-
A.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
B.
warOfIndependence
Indicates a conflict in which a group seeks to gain political independence from a ruling power or colonial authority.
-
C.
notableRevolt
chosen
Indicates a significant uprising or rebellion in which the subject played an important or historically notable role.
-
D.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
E.
firstMajorUprisingEndDate
Indicates the date on which the first major uprising associated with the subject came to an end.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e51817c8190bff50f2c3b5deea0 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.