Triple
T3496175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroes and Villains – lyrics |
E73856
|
entity |
| Predicate | firstOfficialReleaseYear |
P40835
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Heroes and Villains – lyrics, firstOfficialReleaseYear, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOfficialReleaseYear Context triple: [Heroes and Villains – lyrics, firstOfficialReleaseYear, 1967]
-
A.
firstCommercialReleaseYear
chosen
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
-
B.
firstProductionYear
Indicates the year in which something (such as a product, work, or item) was first produced.
-
C.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
D.
firstGenerationReleaseDate
Indicates the calendar date on which the first generation or initial version of something was officially released.
-
E.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbb06fd08190b6c1fadfce4148f0 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.