Triple
T1470952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock and Roll Hall of Fame |
E27132
|
entity |
| Predicate | firstInductionCeremony |
P25710
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Rock and Roll Hall of Fame, firstInductionCeremony, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstInductionCeremony Context triple: [Rock and Roll Hall of Fame, firstInductionCeremony, 1986]
-
A.
hasInductionCeremony
Indicates that an entity conducts or is associated with a formal induction ceremony marking the official admission of individuals into a group, role, or organization.
-
B.
firstInductions
Indicates that the subject entity represents the earliest or initial instances in a series of inductions associated with the object entity.
-
C.
firstCeremony
Indicates that an entity participates in or is associated with the earliest or initial ceremony in a sequence or context.
-
D.
inductedInto
Indicates that an entity has been formally admitted or entered into a group, organization, hall of fame, or similar body, typically as an honor or official recognition.
-
E.
ceremonyYear
chosen
Indicates the year in which a particular ceremony took place.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d9dd4c8190ba840a9255cd1293 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.