Triple
T13760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific War |
E275
|
entity |
| Predicate | combatantStrength |
P1404
|
FINISHED |
| Object | millions of military personnel |
—
|
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: millions of military personnel | Statement: [Pacific War, combatantStrength, millions of military personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantStrength Context triple: [Pacific War, combatantStrength, millions of military personnel]
-
A.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
C.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a243abb2ec8190937365e5ecec52ad |
completed | Feb. 28, 2026, 1:23 a.m. |
| PD | Predicate disambiguation | batch_69a23fe9470c8190918a6ca1df168646 |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a243aa85848190813154e8a6495200 |
completed | Feb. 28, 2026, 1:23 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.