Triple
T29080152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul R. Brown |
E733951
|
entity |
| Predicate | worksInMedia |
P47936
|
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: [Paul R. Brown, worksInMedia, film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksInMedia Context triple: [Paul R. Brown, worksInMedia, film]
-
A.
mediaWorkedFor
Indicates that a media-related entity (such as a journalist, reporter, or media professional) was employed by or had a working affiliation with a particular organization or outlet.
-
B.
developerOfWorkAppearingIn
Indicates that one entity is the creator or developer of a work in which another entity appears or is featured.
-
C.
mediaWork
Indicates a relationship where one entity is a media-related work (such as a film, book, recording, or other creative media production) associated with another entity.
-
D.
workedInMedium
chosen
Indicates that an entity carried out work or activities within a particular medium or channel of expression or communication.
-
E.
usedInMediaOf
Indicates that something (e.g., a work, element, or content) is employed or appears within a particular media work or production.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 10:54 a.m.