Triple
T32720326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redstone 5 |
E836652
|
entity |
| Predicate | containsPerformanceImprovements |
P201347
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Redstone 5, containsPerformanceImprovements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPerformanceImprovements Context triple: [Redstone 5, containsPerformanceImprovements, true]
-
A.
containsSecurityImprovements
Indicates that one entity includes or incorporates enhancements related to safety or security measures in another entity.
-
B.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
C.
performanceImprovementReason
Indicates the reason or cause behind an observed or intended improvement in performance.
-
D.
hasLightingImprovements
Indicates that an entity has enhancements or upgrades made to its lighting conditions or systems.
-
E.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
- F. None of above. chosen
Provenance (4 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
| PDg | Predicate description generation | batch_69ffecdbe62081909f901e7d4db69d60 |
completed | May 10, 2026, 2:26 a.m. |
Created at: May 1, 2026, 1:11 a.m.