Triple
T32720327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redstone 5 |
E836652
|
entity |
| Predicate | containsStabilityImprovements |
P201362
|
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, containsStabilityImprovements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStabilityImprovements Context triple: [Redstone 5, containsStabilityImprovements, true]
-
A.
containsPerformanceImprovements
Indicates that one entity includes or introduces enhancements that improve the performance of another entity or process.
-
B.
containsSecurityImprovements
Indicates that one entity includes or incorporates enhancements related to safety or security measures in another entity.
-
C.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
D.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
E.
hasStabilityLevel
Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
- 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_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
| PDg | Predicate description generation | batch_69ffed884b908190b12422c790b1525e |
completed | May 10, 2026, 2:29 a.m. |
Created at: May 1, 2026, 1:11 a.m.