Triple
T30900891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Falkenstein |
E787162
|
entity |
| Predicate | backedProduction |
P69572
|
FINISHED |
| Object | Lucky Guy |
—
|
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: Lucky Guy | Statement: [Eric Falkenstein, backedProduction, Lucky Guy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backedProduction Context triple: [Eric Falkenstein, backedProduction, Lucky Guy]
-
A.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
B.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
C.
backedProject
chosen
Indicates that one entity has provided support or resources, typically financial, to help initiate or sustain another entity’s project.
-
D.
basedOnProduction
Indicates that one entity is derived from, adapted from, or created using the content, process, or results of another production.
-
E.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923fecf88190813c4df19f69a80d |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:50 p.m.