Triple
T30139690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denny Regrade |
E766093
|
entity |
| Predicate | notableRegradePhase |
P207213
|
FINISHED |
| Object | Denny Regrade No. 1 |
E766093
|
NE 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: Denny Regrade No. 1 | Statement: [Denny Regrade, notableRegradePhase, Denny Regrade No. 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRegradePhase Context triple: [Denny Regrade, notableRegradePhase, Denny Regrade No. 1]
-
A.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
B.
notablePass
Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
-
C.
notableRuleChange
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
D.
notableMode
Indicates that the subject is recognized for or distinguished by the specified mode, manner, or method of operation or expression.
-
E.
notableReaccession
Indicates a significant or noteworthy instance of something being reacquired, reaccepted, or readmitted after having previously left or been removed.
- F. None of above. chosen
Provenance (5 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a274cb85248819085bba59e37129680 |
completed | June 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 7:17 p.m.