Triple
T4943075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clyde Tombaugh |
E110982
|
entity |
| Predicate | hasPartOfCrematedRemains |
P16657
|
FINISHED |
| Object | onboard NASA New Horizons spacecraft |
—
|
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: onboard NASA New Horizons spacecraft | Statement: [Clyde Tombaugh, hasPartOfCrematedRemains, onboard NASA New Horizons spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartOfCrematedRemains Context triple: [Clyde Tombaugh, hasPartOfCrematedRemains, onboard NASA New Horizons spacecraft]
-
A.
crematedBy
Indicates that an entity was cremated through the action or agency of another entity.
-
B.
finalDispositionOfRemains
chosen
Indicates the relationship specifying how a person's physical remains are ultimately handled, treated, or placed after death.
-
C.
hasPartInMausoleum
Indicates that an entity is a component, section, or element contained within or forming part of a mausoleum.
-
D.
hasPartInMannerOfDeath
Indicates that an entity’s involvement in a death is characterized or qualified by a specific manner or way in which the death occurred.
-
E.
cremationPlace
Indicates the place where a person or entity was cremated.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a7650c8190b046b65072fd8eae |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.