Triple
T15337082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Ch'ongch'on River |
E366693
|
entity |
| Predicate | UNObjective |
P56726
|
FINISHED |
| Object | advance to the Yalu River |
—
|
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: advance to the Yalu River | Statement: [Battle of the Ch'ongch'on River, UNObjective, advance to the Yalu River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNObjective Context triple: [Battle of the Ch'ongch'on River, UNObjective, advance to the Yalu River]
-
A.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
B.
actorObjective
chosen
Indicates that an actor has a specific goal, purpose, or intended outcome in relation to another entity or situation.
-
C.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
-
D.
primaryUnionObjective
Indicates the main goal or purpose that a union seeks to achieve in its activities or negotiations.
-
E.
insurgentObjective
Indicates that an insurgent group or actor has a specific strategic goal, target, or desired outcome they are attempting to achieve.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e11b22c81908280efe65acd5454 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.