Triple
T1287745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Lightning |
E27472
|
entity |
| Predicate | isAdaptedAs |
P1926
|
FINISHED |
| Object | radio drama |
—
|
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: radio drama | Statement: [Summer Lightning, isAdaptedAs, radio drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdaptedAs Context triple: [Summer Lightning, isAdaptedAs, radio drama]
-
A.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
-
B.
adaptedTo
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
-
C.
adaptedAs
chosen
Indicates that one work, concept, or entity has been transformed or re-created into another form or medium based on the original.
-
D.
adaptationStatus
Indicates the current state or progress of how something has been adapted or adjusted in response to specific conditions, requirements, or contexts.
-
E.
isFrequentlyAdapted
Indicates that a work or source material is often transformed or re-created into new formats or versions, such as films, plays, or other media.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d1a5508190b4461df77f560df4 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.