Triple
T36828449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlueGene/L |
E910071
|
entity |
| Predicate | heldTop500Rank1Until |
P131385
|
FINISHED |
| Object | 2007-06 |
—
|
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: 2007-06 | Statement: [BlueGene/L, heldTop500Rank1Until, 2007-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTop500Rank1Until Context triple: [BlueGene/L, heldTop500Rank1Until, 2007-06]
-
A.
dateReachedTop500Rank1
Indicates that an entity has, at least once, achieved a ranking within the top 500 positions.
-
B.
wasRankedWorldNumberOneUntil
chosen
Indicates that an entity held the world number one ranking in a given domain up to, but not beyond, a specified time.
-
C.
peakedWithinTopTenOn
Indicates that something (such as a work, product, or performance) reached a highest ranking position within the top ten on a specified chart, list, or ranking system.
-
D.
isConsistentlyRankedInTop
Indicates that an entity repeatedly appears within the top positions of a ranking or list over a sustained period or across multiple evaluations.
-
E.
eloHighestRanking
Indicates that one entity holds the highest Elo rating or ranking within a specified group or context relative to other entities.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.