Triple
T36577969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1940 Whipple |
E902308
|
entity |
| Predicate | eponymHasNotableWorkOn |
P118673
|
FINISHED |
| Object | comets |
—
|
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: comets | Statement: [1940 Whipple, eponymHasNotableWorkOn, comets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eponymHasNotableWorkOn Context triple: [1940 Whipple, eponymHasNotableWorkOn, comets]
-
A.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
B.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
C.
isFamousWorkOf
Indicates that one entity is a well-known or widely recognized work created by another entity (typically an artist, author, or creator).
-
D.
eponymFieldOfWork
chosen
Indicates that a person is the namesake (eponym) of a particular field of work, discipline, or domain.
-
E.
authorNotableWork
Indicates that a person is the creator or writer of a specific notable work, such as a book, article, or other significant publication.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.