Triple
T32296128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Short-Timers |
E825102
|
entity |
| Predicate | coBasisOfAdaptationWith |
P36849
|
FINISHED |
| Object | The Phantom Blooper |
—
|
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: The Phantom Blooper | Statement: [The Short-Timers, coBasisOfAdaptationWith, The Phantom Blooper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coBasisOfAdaptationWith Context triple: [The Short-Timers, coBasisOfAdaptationWith, The Phantom Blooper]
-
A.
hasHumanAdaptation
Indicates that something has been modified, designed, or adjusted specifically to suit human use, abilities, or needs.
-
B.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
C.
basedOnAdaptationsOf
chosen
Indicates that something is derived from or created using one or more prior adaptations of an original work, rather than directly from the original source.
-
D.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
E.
regionOfAdaptation
Indicates the geographic or environmental region to which an entity is specifically adapted.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd3be16081909465eb41815bb768 |
completed | May 3, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:44 a.m.