Triple
T36828478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlueGene/L |
E910071
|
entity |
| Predicate | yearOfDeployment |
P48905
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [BlueGene/L, yearOfDeployment, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfDeployment Context triple: [BlueGene/L, yearOfDeployment, 2004]
-
A.
deploymentYear
chosen
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
B.
eraOfDeployment
Indicates the time period or historical era during which something was put into use or made operational.
-
C.
depositionYear
Indicates the calendar year in which something (such as a document, sample, or item) was formally deposited or submitted.
-
D.
yearOfLaunch
Indicates the specific calendar year in which an entity (such as a product, mission, or project) was first launched or released.
-
E.
landerDeploymentDate
Indicates the date on which a lander is deployed or placed into its intended operational environment.
- 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_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.