Triple
T13708436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gros Ventre people |
E328704
|
entity |
| Predicate | historicalPeriodOfHorseAdoption |
P84186
|
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: [Gros Ventre people, historicalPeriodOfHorseAdoption, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfHorseAdoption Context triple: [Gros Ventre people, historicalPeriodOfHorseAdoption, 18th century]
-
A.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
B.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
-
C.
historicallyAdoptedBy
Indicates that something (such as a practice, policy, idea, or object) was used or taken up by an entity at some point in the past.
-
D.
historicalPeriodOfIntensiveSettlement
Indicates the time span during which a place experienced particularly dense or concentrated settlement activity.
-
E.
timePeriodOfAdoption
chosen
Indicates the specific time period during which something was adopted or came into use.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad18d48c8190a26be865c31975d6 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.