Triple
T31352088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Dat Ninja |
E799622
|
entity |
| Predicate | fictionalReleaseFormat |
P16443
|
FINISHED |
| Object | theatrical film |
—
|
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: theatrical film | Statement: [Who Dat Ninja, fictionalReleaseFormat, theatrical film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalReleaseFormat Context triple: [Who Dat Ninja, fictionalReleaseFormat, theatrical film]
-
A.
hasFormatInFiction
Indicates that a work of fiction is presented or realized in a particular narrative or media format (e.g., novel, film, comic).
-
B.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
-
C.
fictionalMedium
chosen
Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
-
D.
fictionalBroadcastType
Indicates that the relationship specifies the type or category of a fictional broadcast associated with an entity.
-
E.
fictionalMaterial
Indicates that something is made of, composed of, or incorporates a material that exists only in fiction or imagination.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 29, 2026, 9:17 p.m.