Triple
T32707755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asymmetrical Productions |
E836318
|
entity |
| Predicate | backedProjectsBy |
P69572
|
FINISHED |
| Object | David Lynch |
—
|
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: David Lynch | Statement: [Asymmetrical Productions, backedProjectsBy, David Lynch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backedProjectsBy Context triple: [Asymmetrical Productions, backedProjectsBy, David Lynch]
-
A.
backedProject
chosen
Indicates that one entity has provided support or resources, typically financial, to help initiate or sustain another entity’s project.
-
B.
fundedProject
Indicates that a funding entity has provided financial support to a specific project.
-
C.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
D.
byProject
Indicates that something is organized, grouped, or associated according to a specific project.
-
E.
projectsBetween
Indicates a relationship where something is projected or extends from one entity to another across an intervening space or set of entities.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c852d7248190bdf8d128992668cf |
completed | May 3, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:10 a.m.