Triple
T4588252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foal Eagle |
E103420
|
entity |
| Predicate | statusChangeReason |
P5019
|
FINISHED |
| Object | diplomatic engagement with North Korea |
—
|
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: diplomatic engagement with North Korea | Statement: [Foal Eagle, statusChangeReason, diplomatic engagement with North Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusChangeReason Context triple: [Foal Eagle, statusChangeReason, diplomatic engagement with North Korea]
-
A.
statusChange
Indicates a transition in an entity’s state or condition from one status to another over time.
-
B.
statusChangeRule
Indicates a rule or condition that governs how and when an entity’s status is allowed to change from one state to another.
-
C.
changeReason
chosen
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592115fc8190b1aee1d8bbaf1ee3 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.