Triple
T32246204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EasyRiderFranchise |
E823753
|
entity |
| Predicate | originatedFromWork |
P25740
|
FINISHED |
| Object | Easy Rider |
—
|
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: Easy Rider | Statement: [EasyRiderFranchise, originatedFromWork, Easy Rider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedFromWork Context triple: [EasyRiderFranchise, originatedFromWork, Easy Rider]
-
A.
originatesFromWork
chosen
Indicates that something has its source, derivation, or creation in a particular work (such as a document, artwork, or publication).
-
B.
originallyFromWorkType
Indicates that one entity was derived, adapted, or sourced from an original work of a specified type (e.g., book, film, artwork).
-
C.
isFromWorkCreatedIn
Indicates that something originates from or is derived from a work that was created in a specific context, such as a place, time, or setting.
-
D.
workedFrom
Indicates that an entity was employed or actively engaged in work starting from a specified point in time.
-
E.
originatedInWorkBy
Indicates that something was created, derived, or first appeared within a particular work produced by a specific creator.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a017e7bdfe481909cb4d5bdede6035e |
completed | May 11, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_6a017defee108190bdf5f98dc415b250 |
completed | May 11, 2026, 6:57 a.m. |
Created at: May 1, 2026, 12:40 a.m.