Triple
T30428697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iOS 11 |
E774099
|
entity |
| Predicate | latestMajorUpdateVersion |
P168244
|
FINISHED |
| Object | 11.4.1 |
—
|
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: 11.4.1 | Statement: [iOS 11, latestMajorUpdateVersion, 11.4.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestMajorUpdateVersion Context triple: [iOS 11, latestMajorUpdateVersion, 11.4.1]
-
A.
latestMajorUpdate
Indicates the most recent significant update event or version associated with an entity.
-
B.
latestMajorVersionNumber
chosen
Indicates the relationship that specifies the most recent major version number associated with an entity.
-
C.
latestMinorVersion
Indicates that one version is the most recent minor (non-major) update within the series of versions derived from another version.
-
D.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
E.
latestMajorVersionFamily
Indicates that one entity is the most recent major version within a defined version family or series relative to another 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866aa9f88190b3e139fb374d6606 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:06 p.m.