Triple
T17090154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West-Central Korea |
E414701
|
entity |
| Predicate | sawLargeScaleOffensivesBy |
P55964
|
FINISHED |
| Object | Chinese forces |
—
|
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: Chinese forces | Statement: [West-Central Korea, sawLargeScaleOffensivesBy, Chinese forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawLargeScaleOffensivesBy Context triple: [West-Central Korea, sawLargeScaleOffensivesBy, Chinese forces]
-
A.
battleScale
Indicates the relative size or intensity of a battle, such as how large, extensive, or severe the conflict is.
-
B.
numberOfMajorBattles
Indicates the total count of significant or major battles associated with an entity or event.
-
C.
hadMajorOperationsIn
Indicates that an entity has undergone significant or primary operations or activities in a specified location or context.
-
D.
offensiveOperationBy
chosen
Indicates that an offensive military or strategic operation is carried out by a specified actor or entity.
-
E.
offensiveOperation
Indicates an action or campaign in which a party actively initiates hostile or military measures against an opponent.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbf948d88190a4dd4a0774a8505b |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.