Triple
T14973673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Imjin River (1951) |
E373388
|
entity |
| Predicate | UNForcesStrength |
P116901
|
FINISHED |
| Object | approximately 6,000 troops |
—
|
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 6,000 troops | Statement: [Battle of the Imjin River (1951), UNForcesStrength, approximately 6,000 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNForcesStrength Context triple: [Battle of the Imjin River (1951), UNForcesStrength, approximately 6,000 troops]
-
A.
USForceStrength
Indicates the level or magnitude of military forces deployed or available by the United States in a given context.
-
B.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
C.
UnionForcesStrength
Indicates the level or magnitude of military power possessed by Union forces in a given context.
-
D.
strengthGovernmentForces
Indicates the level or degree of military or coercive power held or exerted by government forces in a given context.
-
E.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
- F. None of above. chosen
Provenance (4 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e767608190940eb6f16ea97451 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:50 a.m.