Triple
T35629877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volterra crater |
E1029553
|
entity |
| Predicate | hasInteriorAlbedo |
P198949
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Volterra crater, hasInteriorAlbedo, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorAlbedo Context triple: [Volterra crater, hasInteriorAlbedo, low]
-
A.
hasAlbedo
Indicates that an entity possesses a specific reflectivity or albedo value, describing how much incoming light it reflects.
-
B.
albedoType
Indicates the type or classification of an object's albedo, specifying the nature or category of its reflectivity characteristics.
-
C.
hasHighAlbedo
Indicates that the subject reflects a large proportion of incoming light or radiation from its surface.
-
D.
hasLowAlbedo
chosen
Indicates that an entity reflects only a small fraction of incoming light or radiation, absorbing most of it instead.
-
E.
hasAlbedoFeatureName
Indicates that an entity has or is associated with a specific named albedo (surface reflectivity) feature.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
Created at: May 3, 2026, 4:05 p.m.