Triple
T5273273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L.A. Confidential (1997 film score) |
E119311
|
entity |
| Predicate | originalReleaseMedium |
P22610
|
FINISHED |
| Object | film soundtrack |
—
|
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: film soundtrack | Statement: [L.A. Confidential (1997 film score), originalReleaseMedium, film soundtrack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalReleaseMedium Context triple: [L.A. Confidential (1997 film score), originalReleaseMedium, film soundtrack]
-
A.
originalRelease
Indicates the initial publication or first official release event of a work or product.
-
B.
firstReleaseFormat
chosen
Indicates the original medium or format in which something (such as a work or product) was first released.
-
C.
physicalReleaseDate
Indicates the calendar date on which a work is first made available in a tangible, physical format (e.g., disc, print, cartridge).
-
D.
notableRecordingMedium
Indicates that an entity is notably recorded, documented, or expressed using a particular medium or format.
-
E.
originallyReleasedOn
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.