Triple
T30076444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying French Fries |
E764332
|
entity |
| Predicate | hasCreatorRoleOfCoosjeVanBruggen |
P48506
|
FINISHED |
| Object | co-creator |
—
|
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: co-creator | Statement: [Flying French Fries, hasCreatorRoleOfCoosjeVanBruggen, co-creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatorRoleOfCoosjeVanBruggen Context triple: [Flying French Fries, hasCreatorRoleOfCoosjeVanBruggen, co-creator]
-
A.
hasCreatorRoleFor
chosen
Indicates that an entity serves in the role of creator for another entity, establishing a creator-to-created relationship.
-
B.
coCreator
Indicates that two or more entities jointly created or produced something together.
-
C.
possibleCreator
Indicates that an entity is a plausible but not definitively confirmed creator or originator of another entity.
-
D.
hasCoFounderRole
Indicates that an entity holds or is assigned the role of co-founder in relation to another entity (such as an organization or project).
-
E.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 7:02 p.m.