Triple
T14006462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ron Stockert |
E336960
|
entity |
| Predicate | bandGainedProminence |
P95265
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Ron Stockert, bandGainedProminence, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandGainedProminence Context triple: [Ron Stockert, bandGainedProminence, 1970s]
-
A.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
B.
bandNotableFor
Indicates that a musical band is especially known or recognized for a particular work, achievement, characteristic, or contribution.
-
C.
helpedBoostProminenceOf
Indicates that one entity contributed to increasing the visibility, recognition, or prominence of another entity.
-
D.
gainedRecognition
chosen
Indicates that an entity received acknowledgment, acclaim, or validation from others for its qualities, actions, or achievements.
-
E.
unitOfProminence
Indicates that one entity specifies the unit or scale in which the prominence or significance of another entity is measured or expressed.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed327d88190a53af5768468a8eb |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.