Triple
T32720296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redstone 5 |
E836652
|
entity |
| Predicate | buildNumberAtRelease |
P166840
|
FINISHED |
| Object | 17763 |
—
|
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: 17763 | Statement: [Redstone 5, buildNumberAtRelease, 17763]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildNumberAtRelease Context triple: [Redstone 5, buildNumberAtRelease, 17763]
-
A.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
B.
builtAgainst
Indicates that one structure or object is constructed directly adjoining and supported by the side or surface of another.
-
C.
betaReleaseDate
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
-
D.
firstStableBuildReleasedOn
Indicates the date on which the first stable (non-beta) build of something was officially released.
-
E.
assemblyNumber
chosen
Indicates the identifying number assigned to a specific assembly within a larger system or collection.
- 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_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:11 a.m.