Triple
T25048627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpher–Bethe–Gamow paper |
E627312
|
entity |
| Predicate | authorOrder |
P160091
|
FINISHED |
| Object | Alpher, Bethe, Gamow |
—
|
NE NERFINISHED |
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: Alpher, Bethe, Gamow | Statement: [Alpher–Bethe–Gamow paper, authorOrder, Alpher, Bethe, Gamow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOrder Context triple: [Alpher–Bethe–Gamow paper, authorOrder, Alpher, Bethe, Gamow]
-
A.
authorOfNamesFor
Indicates that one entity is the creator or originator of the names assigned to another entity or set of entities.
-
B.
authorTitle
Indicates that a person is the creator or writer of a work that bears the specified title.
-
C.
authors
Indicates that one entity is the creator or writer of another entity, such as a document, work, or piece of content.
-
D.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
-
E.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
- 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_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 6:08 a.m.