Triple
T5043941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C/1996 B2 |
E113612
|
entity |
| Predicate | hasNucleusEstimatedDiameter |
P7302
|
FINISHED |
| Object | about 2–4 kilometers |
—
|
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 2–4 kilometers | Statement: [C/1996 B2, hasNucleusEstimatedDiameter, about 2–4 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNucleusEstimatedDiameter Context triple: [C/1996 B2, hasNucleusEstimatedDiameter, about 2–4 kilometers]
-
A.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
B.
approximateDiameter
chosen
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
C.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
-
D.
hasPolarDiameter_km
Indicates the length of an object's diameter measured from pole to pole, expressed in kilometers.
-
E.
meanDiameter_km
Indicates the average diameter of an object or region measured in kilometers.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fc04f08190aba851fa0192d0fb |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.