Triple
T4374649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Why We Fight (film series) |
E98974
|
entity |
| Predicate | firstPartReleaseYear |
P22690
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Why We Fight (film series), firstPartReleaseYear, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPartReleaseYear Context triple: [Why We Fight (film series), firstPartReleaseYear, 1942]
-
A.
firstPartPublicationYear
chosen
Indicates the year in which the first part or installment of a multi-part publication was released.
-
B.
firstSeriesYear
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
-
C.
firstProductionYear
Indicates the year in which something (such as a product, work, or item) was first produced.
-
D.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
E.
firstCommercialReleaseYear
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352222df48190bead639e99635faf |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.