Triple
T22543247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kites |
E557349
|
entity |
| Predicate | hasIntendedMedium |
P148596
|
FINISHED |
| Object | live 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: live performance | Statement: [Kites, hasIntendedMedium, live performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntendedMedium Context triple: [Kites, hasIntendedMedium, live performance]
-
A.
isFromMedium
Indicates that something originates from, is derived from, or was obtained via a particular medium or channel.
-
B.
usesActiveMedium
Indicates that an entity performs an action or operates by employing an active medium as the means or channel for that action or process.
-
C.
hasAdaptedMedium
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).
-
D.
hasIntendedListeningMode
Indicates that an entity is associated with a specific listening configuration or mode that it is designed or intended to use.
-
E.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f33c9cc819086d098f36e4121dc |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.