Triple
T27577376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crying Lightning |
E699493
|
entity |
| Predicate | releasedAs7InchSingle |
P169260
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Crying Lightning, releasedAs7InchSingle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedAs7InchSingle Context triple: [Crying Lightning, releasedAs7InchSingle, true]
-
A.
releasedAsSingleIn
Indicates that a musical work or track was issued as a standalone single in a specific year or time period.
-
B.
releasedAsSingleFor
Indicates that a particular track or song was issued as a standalone single specifically to promote or represent a given album, project, or release.
-
C.
releasedAsDigitalSingle
Indicates that a work was issued or made available specifically in digital format as a standalone single.
-
D.
releasedAsSingleInTerritory
Indicates that a work (such as a song or recording) was issued as a single in a specific geographic territory or market.
-
E.
releasedAsLeadSingle
Indicates that a particular song was issued as the primary or first single promoting a larger music release, such as an album or EP.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 27, 2026, 2:01 p.m.