Triple
T23115863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemical Science |
E576749
|
entity |
| Predicate | hasDigitalIdentifier |
P1285
|
FINISHED |
| Object | 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: ISSN | Statement: [Chemical Science, hasDigitalIdentifier, ISSN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalIdentifier Context triple: [Chemical Science, hasDigitalIdentifier, ISSN]
-
A.
hasDigitalObjectIdentifier
Indicates that an entity is associated with a specific Digital Object Identifier (DOI) that uniquely identifies it in a digital environment.
-
B.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
-
D.
hasDigitalCard
Indicates that an entity possesses or is associated with a digital card (such as an electronic ID, membership, or payment card).
-
E.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e1326f08190a1a0b95396cbcd17 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.