Triple
T1532578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon van der Meer |
E32476
|
entity |
| Predicate | nobelPrizeIn |
P1861
|
FINISHED |
| Object | Physics |
—
|
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: Physics | Statement: [Simon van der Meer, nobelPrizeIn, Physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobelPrizeIn Context triple: [Simon van der Meer, nobelPrizeIn, Physics]
-
A.
NobelPrizeShare
Indicates the proportion or fraction of a Nobel Prize that is allocated to a particular laureate or laureate entity.
-
B.
nobelPrizeRelated
Indicates that there is a connection or association between an entity and the Nobel Prize, such as receiving, being nominated for, or otherwise being significantly linked to it.
-
C.
NobelPrizeCategory
chosen
Indicates the specific Nobel Prize field or discipline (such as Physics, Literature, or Peace) associated with an award or laureate.
-
D.
roleInNobelPrize
Indicates the specific capacity or function an entity had in relation to a particular Nobel Prize (e.g., laureate, nominee, organization, or associated role).
-
E.
NobelPrize.motivation
Indicates the official reason or justification given for awarding a particular Nobel Prize.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a915f323bc8190aa757142c225e0ae |
completed | March 5, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69a907b046448190be8ea4d7b20255f7 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.