Triple
T26917186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOSPR |
E677546
|
entity |
| Predicate | specialFocus |
P168069
|
FINISHED |
| Object | 20th-century music |
—
|
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: 20th-century music | Statement: [NOSPR, specialFocus, 20th-century music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialFocus Context triple: [NOSPR, specialFocus, 20th-century music]
-
A.
focusTrait
Indicates that one entity is characterized by, or primarily associated with, a particular trait or attribute of another entity.
-
B.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
C.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
D.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
E.
focusFeature
Indicates that one entity is the primary or emphasized feature, aspect, or attribute being highlighted or concentrated on in relation to another.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 6:05 a.m.