Triple
T10570514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Rosebud |
E249465
|
entity |
| Predicate | hasBelligerentStrength |
P87717
|
FINISHED |
| Object | about 1,300 U.S. 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: about 1,300 U.S. soldiers and scouts | Statement: [Battle of the Rosebud, hasBelligerentStrength, about 1,300 U.S. soldiers and scouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBelligerentStrength Context triple: [Battle of the Rosebud, hasBelligerentStrength, about 1,300 U.S. soldiers and scouts]
-
A.
hasApproximateDefendingForceSize
chosen
Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
-
B.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
C.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
D.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
E.
hasReserveForces
Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5274678148190b7a1afc099628357 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.