Triple
T23487063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Impact |
E570562
|
entity |
| Predicate | impactorMass |
P26037
|
FINISHED |
| Object | about 370 kilograms |
—
|
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: about 370 kilograms | Statement: [Deep Impact, impactorMass, about 370 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactorMass Context triple: [Deep Impact, impactorMass, about 370 kilograms]
-
A.
impactorDiameter
Indicates the size of the object that impacts another body, typically measured as the diameter of the impacting body.
-
B.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
-
C.
usedTargetMass
Indicates that an action or process utilized a specific mass or quantity of a target entity.
-
D.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
-
E.
hasMass_kg
chosen
Indicates that an entity possesses a specific mass measured in kilograms.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a754825481909b005ca5654c3159 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.