Triple
T26692257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobel Prize in Chemistry 1904 |
E672916
|
entity |
| Predicate | hasLaureateOccupation |
P132716
|
FINISHED |
| Object | chemist |
—
|
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: chemist | Statement: [Nobel Prize in Chemistry 1904, hasLaureateOccupation, chemist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaureateOccupation Context triple: [Nobel Prize in Chemistry 1904, hasLaureateOccupation, chemist]
-
A.
laureateOccupation
chosen
Indicates the professional role or field in which a laureate is recognized or has worked.
-
B.
hasLaureate
Indicates that an entity (such as an award or prize) has a specific person or group as its laureate or recipient.
-
C.
hasLaureateField
Indicates that an entity recognized as a laureate is associated with a particular field or discipline in which the honor was awarded.
-
D.
hasLaureateTitle
Indicates that an entity holds or is designated with a laureate title or honor (such as a prize or award laureateship).
-
E.
NobelPrizeCoLaureate
Indicates that two or more individuals share the same Nobel Prize as co-recipients for a particular award and year.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 3:26 a.m.