Triple
T33773772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javelin Productions |
E865455
|
entity |
| Predicate | involvedInCreationOf |
P107257
|
FINISHED |
| Object | Sense8 |
—
|
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: Sense8 | Statement: [Javelin Productions, involvedInCreationOf, Sense8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedInCreationOf Context triple: [Javelin Productions, involvedInCreationOf, Sense8]
-
A.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
B.
workProducedBy
chosen
Indicates that a particular work (such as a creation, product, or result) was created, generated, or authored by a specific agent or entity.
-
C.
hasInventorRoleOf
Indicates that an entity holds or fulfills the role of inventor with respect to another entity (such as an invention, patent, or creative work).
-
D.
workedAsProducerFor
Indicates that one entity served in the role of producer for a work, project, or production associated with another entity.
-
E.
associatedActOfCreator
Indicates a relationship where an act is linked to the creator responsible for or connected with that act.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:45 a.m.