Triple
T10709491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Tongue River (1876) |
E252493
|
entity |
| Predicate | U.S. strength |
P11878
|
FINISHED |
| Object | approximately 379 soldiers and scouts |
—
|
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: approximately 379 soldiers and scouts | Statement: [Battle of the Tongue River (1876), U.S. strength, approximately 379 soldiers and scouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: U.S. strength Context triple: [Battle of the Tongue River (1876), U.S. strength, approximately 379 soldiers and scouts]
-
A.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
B.
U.S.component
Indicates that something is a constituent part, subdivision, or member unit within the United States.
-
C.
objectiveOfUnitedStates
Indicates that something is an official objective or goal pursued by the United States.
-
D.
warTimeStrengthApprox
chosen
Indicates an approximate measure of an entity’s military strength or capacity during a time of war.
-
E.
formerUSExpansion
Indicates that an entity previously expanded into or operated within the United States but no longer does so.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe515b1081909532a20b61ff6cf0 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.