Triple
T37159437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick Whitman |
E920604
|
entity |
| Predicate | identityChangeTriggeredBy |
P110630
|
FINISHED |
| Object | explosion in 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: explosion in Korea | Statement: [Dick Whitman, identityChangeTriggeredBy, explosion in Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identityChangeTriggeredBy Context triple: [Dick Whitman, identityChangeTriggeredBy, explosion in Korea]
-
A.
identityUsedBy
Indicates that a particular identity is being employed or utilized by a specific entity.
-
B.
roleReplacedOn
Indicates that one role has been substituted or taken over by another role at a specific point in time.
-
C.
nameChangeAssociatedWith
Indicates that a change in one entity’s name is linked or correlated with a change or event involving another entity.
-
D.
identityMovement
Indicates a change or transformation in an entity’s identity, status, or self-conception over time or across contexts.
-
E.
changedUnder
chosen
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.