Triple
T25387792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sun, Whose Rays Are All Ablaze |
E631571
|
entity |
| Predicate | premiereCityWork |
P3172
|
FINISHED |
| Object | London |
—
|
NE NERFINISHED |
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: London | Statement: [The Sun, Whose Rays Are All Ablaze, premiereCityWork, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereCityWork Context triple: [The Sun, Whose Rays Are All Ablaze, premiereCityWork, London]
-
A.
premiereWithWork
Indicates that a performance, event, or production debuts at the same time as (or as part of) the first public presentation of a specific work.
-
B.
premiereWork
Indicates that a creative work is the first or debut piece presented or introduced by a particular creator or entity.
-
C.
premiereLocation
chosen
Indicates the place where something (such as a film, play, or event) is first publicly presented or debuted.
-
D.
premiereWorkPlace
Indicates the place where a work (such as a performance, film, or exhibition) is first publicly premiered.
-
E.
premiereWorkComposer
Indicates that the linked composer is the creator of the work being identified as a premiere or first performance piece.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656c16ac8190be99d40cb63f9541 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:47 p.m.