Triple
T31981290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Prayer |
E816586
|
entity |
| Predicate | nominatedFor |
P1791
|
FINISHED |
| Object |
NME Award for Best Track
The NME Award for Best Track is a music award presented by the British magazine NME to recognize the standout song of the year.
|
E230472
|
NE 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: NME Award for Best Track | Statement: [The Prayer, nominatedFor, NME Award for Best Track]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: NME Award for Best Track Triple: [The Prayer, nominatedFor, NME Award for Best Track]
Generated description
The NME Award for Best Track is a music award presented by the British magazine NME to recognize the standout song of the year.
Provenance (5 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b34d116c81908086e458fe8bf42e |
completed | May 3, 2026, 2:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb15103488190a887e25ae7018a5f |
completed | June 14, 2026, 1:49 p.m. |
| NEDg | Description generation | batch_6a2eb1e890dc8190b9948d105e53e444 |
completed | June 14, 2026, 1:51 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a2eb29420988190a93593427ea8715a |
completed | June 14, 2026, 1:54 p.m. |
Created at: May 1, 2026, 12:11 a.m.