Triple
T2352352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamlet (1996 film) |
E47475
|
entity |
| Predicate | screenAspectRatio |
P1991
|
FINISHED |
| Object | 2.20:1 |
—
|
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: 2.20:1 | Statement: [Hamlet (1996 film), screenAspectRatio, 2.20:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenAspectRatio Context triple: [Hamlet (1996 film), screenAspectRatio, 2.20:1]
-
A.
aspectRatio
chosen
Indicates the proportional relationship between an entity’s width and its height.
-
B.
mediaAspect
Indicates the specific aspect ratio or dimensional proportion of a media item in relation to its width and height.
-
C.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
D.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
E.
pegRatio
Indicates the relationship between a company’s price-to-earnings (P/E) ratio and its expected earnings growth rate, expressing how highly the market values each unit of anticipated growth.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.