Triple
T32114181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Dynamic Digital Sound |
E820193
|
entity |
| Predicate | firstMajorRelease |
P26985
|
FINISHED |
| Object | Last Action Hero |
E185822
|
NE 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: Last Action Hero | Statement: [Sony Dynamic Digital Sound, firstMajorRelease, Last Action Hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorRelease Context triple: [Sony Dynamic Digital Sound, firstMajorRelease, Last Action Hero]
-
A.
firstMajorDevelopment
Indicates that the object is the earliest significant development, milestone, or major advancement associated with the subject.
-
B.
firstMajorVersionBy
Indicates that one entity is the earliest or initial major version created or released by another entity.
-
C.
firstRelease
chosen
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
D.
firstMajorRevisionDate
Indicates the date on which an entity underwent its first significant or major revision.
-
E.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
- F. None of above.
Provenance (4 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0125faa88190829aa632d2d4b87c |
completed | June 14, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:28 a.m.