Triple
T32720318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redstone 5 |
E836652
|
entity |
| Predicate | majorUpdateNumber |
P10600
|
FINISHED |
| Object | fifth Redstone update |
—
|
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: fifth Redstone update | Statement: [Redstone 5, majorUpdateNumber, fifth Redstone update]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorUpdateNumber Context triple: [Redstone 5, majorUpdateNumber, fifth Redstone update]
-
A.
majorUpdate
Indicates that a substantial or significant change or revision has been made to something, typically altering its core features or functionality.
-
B.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
-
C.
majorVersion
chosen
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
D.
majorRevisionDate
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
E.
latestMajorUpdate
Indicates the most recent significant update event or version associated with an entity.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 1, 2026, 1:11 a.m.