Triple
T10395971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite from 'High Heels' |
E245017
|
entity |
| Predicate | hasAdaptedMedium |
P93694
|
FINISHED |
| Object | concert performance |
—
|
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: concert performance | Statement: [Suite from 'High Heels', hasAdaptedMedium, concert performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptedMedium Context triple: [Suite from 'High Heels', hasAdaptedMedium, concert performance]
-
A.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
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.
hasMediaAdaptation
Indicates that a work has been adapted into another medium, such as film, television, or other forms of media.
-
D.
hasWorkAdaptation
Indicates that an entity has a modified, adjusted, or alternative form specifically adapted for use in a work or professional context.
-
E.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
- F. None of above. chosen
Provenance (4 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9cf79348190975d6c1791e3b621 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:06 p.m.