Triple
T30825480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Deadly Attachment |
E785049
|
entity |
| Predicate | hasTimePeriodOfProduction |
P23186
|
FINISHED |
| Object | early 1970s |
—
|
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: early 1970s | Statement: [The Deadly Attachment, hasTimePeriodOfProduction, early 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodOfProduction Context triple: [The Deadly Attachment, hasTimePeriodOfProduction, early 1970s]
-
A.
timePeriodOfProduction
chosen
Indicates the span of time during which something was produced or created.
-
B.
mainProductionPeriodStart
Indicates the point in time when the primary or main phase of production for something begins.
-
C.
modelProduced
Indicates that a particular model has generated or produced a specified output, result, or artifact.
-
D.
hasProductionHistory
Indicates that an entity is associated with a record or account of its past production activities, processes, or outputs.
-
E.
firstProducedFor
Indicates that something was initially created, manufactured, or developed specifically for a particular recipient, purpose, or 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 29, 2026, 8:44 p.m.