Triple
T4007430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donda 2 |
E89558
|
entity |
| Predicate | initialReleaseFormat |
P22610
|
FINISHED |
| Object | digital download |
—
|
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: digital download | Statement: [Donda 2, initialReleaseFormat, digital download]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialReleaseFormat Context triple: [Donda 2, initialReleaseFormat, digital download]
-
A.
firstReleaseFormat
chosen
Indicates the original medium or format in which something (such as a work or product) was first released.
-
B.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
-
C.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
D.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
-
E.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.