Triple
T9395586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodnight Tonight |
E226133
|
entity |
| Predicate | isStandaloneRelease |
P88709
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Goodnight Tonight, isStandaloneRelease, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandaloneRelease Context triple: [Goodnight Tonight, isStandaloneRelease, Yes]
-
A.
isSoloReleaseOf
Indicates that a release is a solo work attributed to a single primary artist, rather than a group or collaboration, for a given musical entity.
-
B.
notStandalone
Indicates that an entity cannot exist, function, or be valid independently and must be associated with or supported by another entity.
-
C.
independentRelease
Indicates that a work was released independently, without the backing or involvement of a major external organization or label.
-
D.
canBeStandaloneName
Indicates that something is suitable to function independently as a complete, self-contained name without requiring additional qualifiers or context.
-
E.
isDeployedFrom
Indicates that one entity originates, is launched, or put into operation from another specified source or location.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5112faa08190a8dd2c461d1e7a14 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:45 p.m.