Triple
T19915626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Death of Klinghoffer |
E478656
|
entity |
| Predicate | firstUSProductionYear |
P39672
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [The Death of Klinghoffer, firstUSProductionYear, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUSProductionYear Context triple: [The Death of Klinghoffer, firstUSProductionYear, 1991]
-
A.
firstProductionYear
chosen
Indicates the year in which something (such as a product, work, or item) was first produced.
-
B.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
C.
firstArrivalYear
Indicates the calendar year in which an entity first arrived at or was initially present in a specified place or context.
-
D.
firstPrototypeYear
Indicates the year in which the first prototype of an entity was created or completed.
-
E.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6599394f081909246006c2e83bacc |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.