Triple
T65174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRLD-TV |
E1296
|
entity |
| Predicate | coveredEvent |
P1664
|
FINISHED |
| Object | assassination of John F. Kennedy |
—
|
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: assassination of John F. Kennedy | Statement: [KRLD-TV, coveredEvent, assassination of John F. Kennedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredEvent Context triple: [KRLD-TV, coveredEvent, assassination of John F. Kennedy]
-
A.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
oversawEvent
Indicates that an entity had supervisory or managerial responsibility for the planning, execution, or overall conduct of an event.
-
C.
event
chosen
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
D.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
E.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.