Triple
T23186009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1552 Bessel |
E579594
|
entity |
| Predicate | honorsWorkIn |
P151276
|
FINISHED |
| Object | astrometry |
—
|
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: astrometry | Statement: [1552 Bessel, honorsWorkIn, astrometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsWorkIn Context triple: [1552 Bessel, honorsWorkIn, astrometry]
-
A.
honoursWorkOn
Indicates that one entity formally recognizes and pays tribute to the work or contributions made by another entity.
-
B.
honorsActivity
Indicates that one entity formally recognizes, celebrates, or pays tribute to an activity or action performed by another entity.
-
C.
notableStudentWork
Indicates that the subject has a student whose work is particularly notable or significant in relation to the subject.
-
D.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
E.
recognizesWorkOf
Indicates that one entity acknowledges, identifies, or gives credit to the work or contributions produced by another entity.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd3aaa08190b9cf7afe4ee5a38d |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:05 p.m.