Triple
T34057867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Touch the Clouds |
E873411
|
entity |
| Predicate | becameChiefOf |
P34999
|
FINISHED |
| Object | Minneconjou Lakota |
—
|
NE NERFINISHED |
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: Minneconjou Lakota | Statement: [Touch the Clouds, becameChiefOf, Minneconjou Lakota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameChiefOf Context triple: [Touch the Clouds, becameChiefOf, Minneconjou Lakota]
-
A.
successorAsChief
Indicates that one entity becomes the next chief, taking over the leadership role from another entity.
-
B.
officeHolderBecame
chosen
Indicates that an individual assumed or transitioned into holding a particular office or official position.
-
C.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
D.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
E.
succeededAsHeadOfHouse
Indicates that one entity took over the role or position of head of a household or family from another entity.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:52 a.m.