Triple
T388878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Applied Physics Letters |
E8838
|
entity |
| Predicate | eISSN |
P132
|
FINISHED |
| Object | 1077-3118 |
—
|
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: 1077-3118 | Statement: [Applied Physics Letters, eISSN, 1077-3118]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eISSN Context triple: [Applied Physics Letters, eISSN, 1077-3118]
-
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.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
C.
isFlagshipJournalOf
Indicates that a particular journal serves as the primary or leading publication associated with a specific organization, field, or publisher.
-
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.
isbn
Indicates that a publication is associated with a specific International Standard Book Number (ISBN) that uniquely identifies it.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5988708190aa86d9460cecf050 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.