Triple
T11995780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clifford |
E285525
|
entity |
| Predicate | primaryAudienceWork |
P61787
|
FINISHED |
| Object | fans of horror-comedy films |
—
|
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: fans of horror-comedy films | Statement: [Clifford, primaryAudienceWork, fans of horror-comedy films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAudienceWork Context triple: [Clifford, primaryAudienceWork, fans of horror-comedy films]
-
A.
targetAudienceOfOriginWork
chosen
Indicates the intended audience or demographic group for which the original work was created.
-
B.
employerFocus
Indicates that an employer directs particular attention, resources, or priority toward a specific subject, group, or area.
-
C.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
D.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903b211688190bfe6dd15c3f96d2f |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.