Triple
T2724997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Days’ Campaign |
E60168
|
entity |
| Predicate | armedForcesSize |
P39448
|
FINISHED |
| Object | tens of thousands of troops involved |
—
|
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: tens of thousands of troops involved | Statement: [Ten Days’ Campaign, armedForcesSize, tens of thousands of troops involved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForcesSize Context triple: [Ten Days’ Campaign, armedForcesSize, tens of thousands of troops involved]
-
A.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
B.
militarySize
Indicates the total number of personnel in a military force, typically including active-duty members and sometimes reserves.
-
C.
warPower
Indicates the authority, capability, or legal power to initiate, conduct, or manage acts of war or armed conflict.
-
D.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
E.
warTimeStrengthApprox
Indicates an approximate measure of an entity’s military strength or capacity during a time of war.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdacd7e24819084a620063e3f7aa4 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.