Triple
T36191293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upside Down Cake |
E1046995
|
entity |
| Predicate | releaseMajorVersionNumber |
P10600
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Upside Down Cake, releaseMajorVersionNumber, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseMajorVersionNumber Context triple: [Upside Down Cake, releaseMajorVersionNumber, 14]
-
A.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
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.
latestMajorVersionNumber
Indicates the relationship that specifies the most recent major version number associated with an entity.
-
E.
releaseGeneration
Indicates that one entity causes or initiates the production or emission of another entity or resource.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:08 p.m.