Triple
T29430157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Planets: Their Origin and Development |
E746404
|
entity |
| Predicate | hasAuthorNobelPrizeFor |
P90396
|
FINISHED |
| Object | discovery of deuterium |
—
|
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: discovery of deuterium | Statement: [The Planets: Their Origin and Development, hasAuthorNobelPrizeFor, discovery of deuterium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorNobelPrizeFor Context triple: [The Planets: Their Origin and Development, hasAuthorNobelPrizeFor, discovery of deuterium]
-
A.
authorNobelLaureate
chosen
Indicates that the author is a recipient of a Nobel Prize.
-
B.
NobelPrizeCoLaureate
Indicates that two or more individuals share the same Nobel Prize as co-recipients for a particular award and year.
-
C.
namedForNobelLaureate
Indicates that one entity bears a name derived from or in honor of a Nobel Prize laureate.
-
D.
authorNobelYear
Indicates the year in which an author received a Nobel Prize.
-
E.
hasAuthorNobelEquivalent
Indicates that the author of the work has received an award considered equivalent in prestige or recognition to a Nobel Prize in their field.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 3:12 p.m.