Triple
T27442348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Bornstein |
E690971
|
entity |
| Predicate | editingRole |
P107303
|
FINISHED |
| Object | film editor on "The Fog" |
—
|
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 editor on "The Fog" | Statement: [Charles Bornstein, editingRole, film editor on "The Fog"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editingRole Context triple: [Charles Bornstein, editingRole, film editor on "The Fog"]
-
A.
editorialRole
Indicates that one entity holds an editorial position or responsibility in relation to another entity, such as a publication, work, or organization.
-
B.
editingIs
Indicates that one entity is performing or undergoing the process of editing another entity.
-
C.
editorOfWork
chosen
Indicates that one entity serves as the editor responsible for preparing, revising, or overseeing the content of a particular work.
-
D.
editorCommunity
Indicates a relationship where an editor is associated with, participates in, or belongs to a particular community.
-
E.
editingBody
Indicates that one entity is serving as the editorial body responsible for reviewing, modifying, or overseeing the content or work 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d8f3abc819088b471db8c3ba3bd |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:45 p.m.