Triple
T27743619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halley’s Comet |
E701919
|
entity |
| Predicate | hasNucleusAlbedo |
P2046
|
FINISHED |
| Object | very low (dark, ~0.04) |
—
|
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: very low (dark, ~0.04) | Statement: [Halley’s Comet, hasNucleusAlbedo, very low (dark, ~0.04)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNucleusAlbedo Context triple: [Halley’s Comet, hasNucleusAlbedo, very low (dark, ~0.04)]
-
A.
hasAlbedo
chosen
Indicates that an entity possesses a specific reflectivity or albedo value, describing how much incoming light it reflects.
-
B.
hasAlbedoFeatureName
Indicates that an entity has or is associated with a specific named albedo (surface reflectivity) feature.
-
C.
hasHighAlbedo
Indicates that the subject reflects a large proportion of incoming light or radiation from its surface.
-
D.
albedoType
Indicates the type or classification of an object's albedo, specifying the nature or category of its reflectivity characteristics.
-
E.
albedoContrast
Indicates the degree to which two surfaces or regions differ in their reflectivity (albedo), typically highlighting contrast in brightness.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 4:13 p.m.