Triple
T23539315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1952 State of the Union Address |
E577694
|
entity |
| Predicate | mentionsConflict |
P152725
|
FINISHED |
| Object | Korean War |
—
|
NE NERFINISHED |
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: Korean War | Statement: [1952 State of the Union Address, mentionsConflict, Korean War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsConflict Context triple: [1952 State of the Union Address, mentionsConflict, Korean War]
-
A.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
B.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
E.
subjectConflict
Indicates that there is a disagreement, clash, or opposing stance between the subject and another party or situation.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1a66b88190811b38523ea606fe |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:10 p.m.