Triple
T4780916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hills cloud |
E106161
|
entity |
| Predicate | hasDensityComparedTo |
P56981
|
FINISHED |
| Object | denser than outer Oort Cloud |
—
|
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: denser than outer Oort Cloud | Statement: [Hills cloud, hasDensityComparedTo, denser than outer Oort Cloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDensityComparedTo Context triple: [Hills cloud, hasDensityComparedTo, denser than outer Oort Cloud]
-
A.
densityComparedTo
chosen
Indicates a comparison between the densities of two entities, specifying which is denser or how their densities relate.
-
B.
hasMeanDensity
Indicates that one entity possesses a specified average mass per unit volume (mean density).
-
C.
isHeavierThan
Indicates that one entity has greater weight or mass than another entity.
-
D.
hasSpecificGravity
Indicates that one entity has a specific gravity value equal to or characteristic of another entity or reference substance.
-
E.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.