Triple
T29601762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planfilm |
E754467
|
entity |
| Predicate | distributedDirector |
P173735
|
FINISHED |
| Object | Orson Welles |
—
|
NE NERFINISHED |
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: Orson Welles | Statement: [Planfilm, distributedDirector, Orson Welles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributedDirector Context triple: [Planfilm, distributedDirector, Orson Welles]
-
A.
distributedFor
Indicates that something is handed out, allocated, or made available for the benefit or use of a particular recipient, purpose, or context.
-
B.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
C.
distributedWith
Indicates that one entity is supplied, packaged, or made available together with another entity as part of the same distribution.
-
D.
distributedRegion
Indicates that something is spread or allocated across a specific geographic or spatial area.
-
E.
distributedThrough
Indicates that something is supplied, delivered, or made available to others by means of a particular channel, intermediary, or distribution method.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 28, 2026, 6:22 p.m.