Triple
T24254843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Spaceman |
E603639
|
entity |
| Predicate | introducedByBand |
P149175
|
FINISHED |
| Object | Kiss |
—
|
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: Kiss | Statement: [The Spaceman, introducedByBand, Kiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedByBand Context triple: [The Spaceman, introducedByBand, Kiss]
-
A.
originatedFromBand
Indicates that an entity (such as a musician or group) originally came from or was formed as part of a particular band.
-
B.
recordedByBandMemberOf
Indicates that a recording was made by an individual who is a member of a specified band.
-
C.
hasOriginBand
Indicates that an entity (such as a musician or musical act) is or was originally a member of a specified band.
-
D.
wereIntroducedBy
chosen
Indicates that one entity became known, presented, or brought to the attention of another entity through the action or mediation of a third party.
-
E.
associatedBandOrigin
Indicates that there is a relationship between a musical band and the geographic place from which that band originates or is closely associated.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8ca4988190b565c2873dc6559d |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.