Triple
T12526484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Washington (various with Native nations) |
E299452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical event collection |
C31592
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical event collection Context triple: [Treaty of Washington (various with Native nations), instanceOf, historical event collection]
-
A.
historic event
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
-
B.
pair of historical events
A pair of historical events is a conceptual grouping of two distinct occurrences from the past that are related by time, cause, theme, or contrast for purposes of comparison or analysis.
-
C.
history organization
A history organization is an entity dedicated to researching, preserving, interpreting, and promoting understanding of past events, cultures, and narratives through activities such as archiving, education, and public outreach.
-
D.
event in ancient history
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
-
E.
historical event participant
A historical event participant is an individual, group, or entity that directly or indirectly takes part in, influences, or is affected by a specific historical occurrence.
- F. None of above. chosen
Provenance (1 batch)
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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.