Triple
T9840994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Eagle |
E239223
|
entity |
| Predicate | wroteOrDictated |
P2831
|
FINISHED |
| Object | account of the Dakota War of 1862 |
—
|
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: account of the Dakota War of 1862 | Statement: [Big Eagle, wroteOrDictated, account of the Dakota War of 1862]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteOrDictated Context triple: [Big Eagle, wroteOrDictated, account of the Dakota War of 1862]
-
A.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
B.
wrote
chosen
Indicates that an entity is the author or creator of a written work involving another entity.
-
C.
written
Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34c920c81909b56ed9936b15f9b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.