Triple
T12906200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America's Greatest Rock and Roll Band |
E308735
|
entity |
| Predicate | appliedToGroupType |
P106955
|
FINISHED |
| Object | rock band |
—
|
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: rock band | Statement: [America's Greatest Rock and Roll Band, appliedToGroupType, rock band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToGroupType Context triple: [America's Greatest Rock and Roll Band, appliedToGroupType, rock band]
-
A.
appliedToEntityType
Indicates that something (such as a rule, constraint, or operation) is specifically applied to entities of a given type.
-
B.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
-
C.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
D.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971831bd48190b0ecd13e7181bbc6 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.