Triple
T25048600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpher–Bethe–Gamow paper |
E627312
|
entity |
| Predicate | journalIssue |
P157919
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Alpher–Bethe–Gamow paper, journalIssue, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journalIssue Context triple: [Alpher–Bethe–Gamow paper, journalIssue, 7]
-
A.
journalVolume
Indicates that one entity is the specific volume designation (e.g., volume number) associated with a particular journal or journal issue.
-
B.
journalType
Indicates the specific category or format of a journal associated with an entity.
-
C.
issn
Indicates that an entity is associated with a specific International Standard Serial Number (ISSN), identifying it as a particular serial publication.
-
D.
currentIssue
Indicates that an entity is the presently relevant or active issue in a given context or discussion.
-
E.
journalUsedFor
Indicates that a particular journal serves as the medium or venue used for a specified purpose, such as publishing, recording, or disseminating content or information.
- F. None of above. chosen
Provenance (4 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4549e7df48190aa0642008f748314 |
completed | May 1, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:08 a.m.