Triple
T14488393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It's My Party |
E359296
|
entity |
| Predicate | hasTargetFormat |
P101458
|
FINISHED |
| Object | radio airplay |
—
|
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 airplay | Statement: [It's My Party, hasTargetFormat, radio airplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetFormat Context triple: [It's My Party, hasTargetFormat, radio airplay]
-
A.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
C.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
D.
hasPlayFormat
chosen
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
E.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930bd1d48190abd6c47da0a3ebc8 |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.