Triple
T18926432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorothy Hill Medal |
E462983
|
entity |
| Predicate | notableNamesakeOccupation |
P133817
|
FINISHED |
| Object | geologist |
—
|
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: geologist | Statement: [Dorothy Hill Medal, notableNamesakeOccupation, geologist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNamesakeOccupation Context triple: [Dorothy Hill Medal, notableNamesakeOccupation, geologist]
-
A.
notableHolderOccupation
Indicates that a person notably associated with an entity (e.g., an award, office, or title) held a particular occupation or professional role.
-
B.
notableOccupationContext
Indicates that the referenced occupation is notable or significant specifically within the given contextual framework or domain.
-
C.
notableCharacterOccupation
Indicates that a notable character is associated with a specific occupation or professional role.
-
D.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
E.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bc36588190ae9cc3b8abf8afd4 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.