Triple
T24795757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discipline |
E620376
|
entity |
| Predicate | laterReissueFormat |
P50239
|
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: [Discipline, laterReissueFormat, digital download]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReissueFormat Context triple: [Discipline, laterReissueFormat, digital download]
-
A.
reissuedOnFormat
Indicates that an item has been reissued in a particular format or medium.
-
B.
subsequentReleaseFormat
chosen
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
C.
laterReReleasedBy
Indicates that an entity was re-released at a later time by a specified agent or organization.
-
D.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
E.
laterIssuedAs
Indicates that one entity (such as a work, edition, or version) was subsequently released or published in the form of another specified 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:48 a.m.