Triple
T245544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Journal of the Electron Devices Society |
E5028
|
entity |
| Predicate | digitalIdentifier |
P3732
|
FINISHED |
| Object | ISSN (online) |
—
|
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: ISSN (online) | Statement: [IEEE Journal of the Electron Devices Society, digitalIdentifier, ISSN (online)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalIdentifier Context triple: [IEEE Journal of the Electron Devices Society, digitalIdentifier, ISSN (online)]
-
A.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
-
C.
isbn
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
-
D.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
E.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d128c0081909908825b302ae635 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.