Triple
T38677960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DiscoVision |
E943808
|
entity |
| Predicate | notableContentLicensor |
P206612
|
FINISHED |
| Object | Universal Pictures |
E9760
|
NE 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: Universal Pictures | Statement: [DiscoVision, notableContentLicensor, Universal Pictures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableContentLicensor Context triple: [DiscoVision, notableContentLicensor, Universal Pictures]
-
A.
notableShowLicensed
Indicates that a show is officially licensed or authorized in a notable or significant way.
-
B.
notableContentType
Indicates the type or category of content for which an entity is notable or best known.
-
C.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
D.
notableAdaptor
Indicates that one entity is a well-known or distinguished adapter of another entity’s work, style, or content.
-
E.
notableStudio
Indicates that an entity is a studio (e.g., film, music, game, or animation studio) that is especially prominent, influential, or widely recognized in relation to the subject entity.
- F. None of above. chosen
Provenance (5 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd4510588190b207f70686b641f3 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:33 p.m.