Triple
T29987341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rock and roll |
E761765
|
entity |
| Predicate | commercialFormat |
P96259
|
FINISHED |
| Object | singles-oriented |
—
|
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: singles-oriented | Statement: [rock and roll, commercialFormat, singles-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialFormat Context triple: [rock and roll, commercialFormat, singles-oriented]
-
A.
commercialForm
chosen
Indicates the commercial or marketed form in which something (such as a product, substance, or medicine) is offered or sold.
-
B.
commercialProduct
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
-
C.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
D.
commercialCategory
Indicates the type of commercial classification or business category under which an entity or transaction is grouped.
-
E.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 6:37 p.m.