Triple
T24782481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hale Prize |
E620033
|
entity |
| Predicate | namedAfterSpecialization |
P86008
|
FINISHED |
| Object | solar astronomer |
—
|
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: solar astronomer | Statement: [Hale Prize, namedAfterSpecialization, solar astronomer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterSpecialization Context triple: [Hale Prize, namedAfterSpecialization, solar astronomer]
-
A.
laterSpecialization
Indicates that one entity becomes a more specialized or refined version of another entity at a later point in time.
-
B.
exportSpecialization
Indicates a relationship where one entity specializes in exporting particular goods, services, or resources to another entity or market.
-
C.
branchSpecialization
Indicates that one branch or subdivision is specialized or focused in a particular area, function, or domain relative to others.
-
D.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
E.
namedAfterInstanceOf
chosen
Indicates that one entity is named after another entity that is an instance of a particular class or type.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410d73b288190995b2ada5788f436 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:45 a.m.