Triple
T16425320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ian Hay |
E398927
|
entity |
| Predicate | hasAdaptedWorkForMedium |
P93694
|
FINISHED |
| Object | stage |
—
|
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: stage | Statement: [Ian Hay, hasAdaptedWorkForMedium, stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptedWorkForMedium Context triple: [Ian Hay, hasAdaptedWorkForMedium, stage]
-
A.
hasAdaptedMedium
chosen
Indicates that an original work has been transformed or adapted into a different medium or format (e.g., book to film, comic to TV series).
-
B.
hasWorkAdaptation
Indicates that an entity has a modified, adjusted, or alternative form specifically adapted for use in a work or professional context.
-
C.
hasWorkAdaptedBy
Indicates that one work has been transformed or re-created into another work, such as through adaptation into a different medium or format.
-
D.
workAdaptedFor
Indicates that one work has been modified or transformed to create another work specifically suited for a different medium, context, or audience.
-
E.
hasWorkAdaptedFrom
Indicates that one work is derived, adapted, or transformed from another pre-existing work.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328faa7448190a2606f1b37ea0a3d |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.