Triple
T21316939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoshone people |
E525495
|
entity |
| Predicate | acquiredHorses |
P38604
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Shoshone people, acquiredHorses, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredHorses Context triple: [Shoshone people, acquiredHorses, 18th century]
-
A.
acquiredHorsesFrom
chosen
Indicates that one entity obtained ownership or control of horses from another entity, typically through purchase, trade, or transfer.
-
B.
ownedRacehorse
Indicates that one entity possessed legal ownership of a particular racehorse.
-
C.
usesHorseType
Indicates that one entity employs, relies on, or operates using a specific type or category of horse.
-
D.
eligibleHorses
Indicates that certain horses meet the required conditions or criteria to qualify for a specified status, event, or action.
-
E.
notableHorse
Indicates that the subject is a horse recognized for particular significance, fame, or distinction.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dd0b34481909dd6d37cf8e42144 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:34 p.m.