Triple
T4696979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Rental (film score) |
E104169
|
entity |
| Predicate | hasOriginalWorkMedium |
P58594
|
FINISHED |
| Object | feature 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: feature film | Statement: [Summer Rental (film score), hasOriginalWorkMedium, feature film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalWorkMedium Context triple: [Summer Rental (film score), hasOriginalWorkMedium, feature film]
-
A.
originalWorkFrom
Indicates that something is derived, adapted, or based on an earlier original work created by another source.
-
B.
hasDerivativeWork
Indicates that one work is based on, adapted from, or otherwise derived from another work.
-
C.
originalPublicationOfWholeWork
Indicates that one entity is the original publication in which an entire work was first made publicly available.
-
D.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
E.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
- F. None of above. chosen
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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:17 p.m.