Triple
T19433639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iOS 15 |
E486179
|
entity |
| Predicate | latestReleaseInMajorVersion |
P33565
|
FINISHED |
| Object | iOS 15.8.2 |
—
|
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: iOS 15.8.2 | Statement: [iOS 15, latestReleaseInMajorVersion, iOS 15.8.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestReleaseInMajorVersion Context triple: [iOS 15, latestReleaseInMajorVersion, iOS 15.8.2]
-
A.
latestMinorVersion
chosen
Indicates that one version is the most recent minor (non-major) update within the series of versions derived from another version.
-
B.
latestMajorUpdate
Indicates the most recent significant update event or version associated with an entity.
-
C.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
D.
latestReleaseBranch
Indicates that a branch is designated as the most recent official release branch in a version control or release management system.
-
E.
latestMajorVersionPublisher
Indicates that the subject is the publisher responsible for releasing the most recent major version of the referenced 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335dae10819096e1825741f814ed |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.