Triple
T26494345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonlight Shadow |
E669240
|
entity |
| Predicate | writtenForAlbum |
P117315
|
FINISHED |
| Object | Crises |
—
|
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: Crises | Statement: [Moonlight Shadow, writtenForAlbum, Crises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenForAlbum Context triple: [Moonlight Shadow, writtenForAlbum, Crises]
-
A.
writtenForPerformer
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
-
B.
workedOnAlbum
Indicates that an entity contributed work or effort to the creation or production of a particular music album.
-
C.
writtenForInstrument
Indicates that a work was specifically composed or arranged to be performed on a particular musical instrument.
-
D.
workWrittenFor
chosen
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
E.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61354e6ac8190b5f8d50db9c45d47 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:07 a.m.