Triple
T2216166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmas Is All Around |
E48036
|
entity |
| Predicate | featuredInWorkType |
P1366
|
FINISHED |
| Object | 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: film | Statement: [Christmas Is All Around, featuredInWorkType, film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInWorkType Context triple: [Christmas Is All Around, featuredInWorkType, film]
-
A.
settingOfWorks
Indicates that a place or environment serves as the primary setting where the events or narratives of one or more works take place.
-
B.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
C.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
D.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc00f4c3881909d03301fcdfa8b67 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.