Triple
T10894903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago 10 |
E257283
|
entity |
| Predicate | hasOriginalReleaseMedium |
P58594
|
FINISHED |
| Object | theatrical film |
—
|
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: theatrical film | Statement: [Chicago 10, hasOriginalReleaseMedium, theatrical film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalReleaseMedium Context triple: [Chicago 10, hasOriginalReleaseMedium, theatrical film]
-
A.
hasReleaseMedium
Indicates the medium or format through which something (such as a work or product) is released or made available.
-
B.
hasOriginalWorkMedium
chosen
Indicates that an original creative work is associated with a specific medium or material in which it was first produced.
-
C.
isOriginalUSPressingOf
Indicates that one item is the first edition or initial manufacturing run of a media release specifically produced and distributed in the United States.
-
D.
hasPhysicalMedium
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
E.
originalRelease
Indicates the initial publication or first official release event of a work or product.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d0153408190bcba2d9b03d78804 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.