Triple
T28206207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PoP! |
E717028
|
entity |
| Predicate | fictionalRecordIndustryContext |
P96045
|
FINISHED |
| Object | 1980s British pop scene |
—
|
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: 1980s British pop scene | Statement: [PoP!, fictionalRecordIndustryContext, 1980s British pop scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalRecordIndustryContext Context triple: [PoP!, fictionalRecordIndustryContext, 1980s British pop scene]
-
A.
fictionalIndustry
Indicates that an entity operates within an industry or sector that exists only in fiction rather than in the real world.
-
B.
hasRecordIndustry
Indicates that an entity is associated with or operates within the record (music) industry.
-
C.
musicIndustry
Indicates a relationship or involvement between entities within the business, production, distribution, or promotion aspects of music.
-
D.
hasFictionalRecordLabel
chosen
Indicates that an entity is associated with a record label that exists only within a fictional or narrative context.
-
E.
recordIndustryCategory
Indicates the industry classification or sector under which an entity’s business activities are recorded.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 10:35 p.m.