Triple
T18104164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulchi Focus Lens |
E433305
|
entity |
| Predicate | scenarioFocus |
P31
|
FINISHED |
| Object | North Korean attack contingency |
—
|
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: North Korean attack contingency | Statement: [Ulchi Focus Lens, scenarioFocus, North Korean attack contingency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scenarioFocus Context triple: [Ulchi Focus Lens, scenarioFocus, North Korean attack contingency]
-
A.
scenarioType
Indicates the specific category or kind of situation, context, or use case that an entity or event is associated with.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
D.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
E.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb8dd308190a9c98ac2b1d8b872 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.