Triple
T22727360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billboard Dance Club Songs chart |
E562030
|
entity |
| Predicate | secondaryFormat |
P43291
|
FINISHED |
| Object | online |
—
|
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: online | Statement: [Billboard Dance Club Songs chart, secondaryFormat, online]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryFormat Context triple: [Billboard Dance Club Songs chart, secondaryFormat, online]
-
A.
secondPartFormat
Indicates that the entity represents the format or structure of the second part or segment of a larger item or sequence.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryContentType
chosen
Indicates the type or category of additional, non-primary content associated with an entity or resource.
-
D.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
-
E.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792a2ee48190bfbdde1a72adfd25 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:20 p.m.