Triple
T27375548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Worthing Yates |
E691056
|
entity |
| Predicate | wroteForFormat |
P164502
|
FINISHED |
| Object | theatrical 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: theatrical film | Statement: [George Worthing Yates, wroteForFormat, theatrical film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteForFormat Context triple: [George Worthing Yates, wroteForFormat, theatrical film]
-
A.
definesFormatFor
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
-
B.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
C.
writtenInForm
Indicates that something is expressed, recorded, or composed using a particular format, style, or structural form.
-
D.
writtenForEvent
Indicates that something (typically a work or piece) was created specifically for a particular event or occasion.
-
E.
originallyWrittenFor
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
- F. None of above. chosen
Provenance (4 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 12:20 p.m.