Triple
T34032185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackfoot Lakota |
E872684
|
entity |
| Predicate | hasHorseCulture |
P172264
|
FINISHED |
| Object | Plains equestrian culture |
—
|
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: Plains equestrian culture | Statement: [Blackfoot Lakota, hasHorseCulture, Plains equestrian culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHorseCulture Context triple: [Blackfoot Lakota, hasHorseCulture, Plains equestrian culture]
-
A.
hasCavalryHeritage
Indicates that an entity has a historical or traditional connection to cavalry forces or mounted military service.
-
B.
usesHorseType
Indicates that one entity employs, relies on, or operates using a specific type or category of horse.
-
C.
horseCulture
chosen
Indicates a cultural relationship in which horses play a central or defining role in the practices, values, or way of life of a group.
-
D.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
E.
hasRacehorseCharacter
Indicates that one entity possesses the traits, qualities, or behavioral characteristics associated with a racehorse in relation to another entity 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 1, 2026, 1:51 a.m.