Triple
T4621323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gall |
E100990
|
entity |
| Predicate | roleAtLittleBighorn |
P28183
|
FINISHED |
| Object | tactical field commander |
—
|
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: tactical field commander | Statement: [Gall, roleAtLittleBighorn, tactical field commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtLittleBighorn Context triple: [Gall, roleAtLittleBighorn, tactical field commander]
-
A.
roleInMexicanAmericanWar
Indicates that an entity participated in the Mexican–American War in a specified capacity or function.
-
B.
NativeAmericanCommander
Indicates that the subject served as a military leader or commander who was Native American in origin or identity in relation to the object (e.g., a battle, force, or unit).
-
C.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
D.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
E.
roleInGoldRush
Indicates that an entity played a specific role or had a particular involvement in the historical event known as the Gold Rush.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e560f481908abb1a97b4ff5795 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.