Triple
T73684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Transactions on Audio, Speech, and Language Processing |
E1475
|
entity |
| Predicate | issnType |
P132
|
FINISHED |
| Object | print ISSN |
—
|
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: print ISSN | Statement: [IEEE Transactions on Audio, Speech, and Language Processing, issnType, print ISSN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issnType Context triple: [IEEE Transactions on Audio, Speech, and Language Processing, issnType, print ISSN]
-
A.
issn
chosen
Indicates that an entity is associated with a specific International Standard Serial Number (ISSN), identifying it as a particular serial publication.
-
B.
isbn
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
-
C.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
D.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
E.
fieldOfPublication
Indicates the academic or topical area in which a work is published.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a252201fa481908e30791954119c17 |
completed | Feb. 28, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69a24eacfdc481909e9ff99752fd42bf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.