Triple
T35505936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISE All-Sky Source Catalog |
E1026150
|
entity |
| Predicate | coversBand |
P192946
|
FINISHED |
| Object | W1 |
—
|
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: W1 | Statement: [WISE All-Sky Source Catalog, coversBand, W1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversBand Context triple: [WISE All-Sky Source Catalog, coversBand, W1]
-
A.
usesBand
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
-
B.
coverPerformer
Indicates that one entity performs a cover version of a work originally created or performed by another entity.
-
C.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
D.
creditedBandType
Indicates that an entity is credited specifically as a band of a particular type or classification in a given context.
-
E.
playedWithBandFrom
Indicates that an individual has performed as a member or guest with a musical band originating from a specified place or organization.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 3, 2026, 4:04 p.m.