Triple
T5743034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis Entertainment |
E126659
|
entity |
| Predicate | activeInMedium |
P54385
|
FINISHED |
| Object | theatrical 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: theatrical films | Statement: [Davis Entertainment, activeInMedium, theatrical films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInMedium Context triple: [Davis Entertainment, activeInMedium, theatrical films]
-
A.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
-
B.
occursInMedium
chosen
Indicates that an event, process, or interaction takes place within or is hosted by a particular medium or environment.
-
C.
mediaActivity
Indicates an action or engagement involving the creation, use, sharing, or interaction with media content.
-
D.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
E.
plannedMedium
Indicates that a particular medium or channel has been designated in advance for use in carrying out an action or communication.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.