Triple
T14599855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Wick (film score) |
E342671
|
entity |
| Predicate | forWorkType |
P86785
|
FINISHED |
| Object | feature 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: feature film | Statement: [John Wick (film score), forWorkType, feature film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forWorkType Context triple: [John Wick (film score), forWorkType, feature film]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
C.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
D.
givenForWorkIn
Indicates that something (such as payment, benefit, or item) is provided to an entity specifically in exchange for or in connection with work performed in a particular role, job, or context.
-
E.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb438748081908020ce04b869866a |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.