Triple
T5051097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phobos |
E113785
|
entity |
| Predicate | hasRegolithDepth |
P60882
|
FINISHED |
| Object | up to about 100 meters |
—
|
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: up to about 100 meters | Statement: [Phobos, hasRegolithDepth, up to about 100 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegolithDepth Context triple: [Phobos, hasRegolithDepth, up to about 100 meters]
-
A.
hasCrustalThickness
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
B.
hasCraterDensity
Indicates a relationship where an entity is characterized by a specific density or concentration of craters on its surface.
-
C.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
D.
hasHeavilyCrateredSurface
Indicates that the subject’s surface is densely covered with impact craters, showing extensive cratering relative to typical surfaces.
-
E.
maximumDepthKilometres
Indicates the greatest depth, measured in kilometers, that something reaches or extends to.
- F. None of above. chosen
Provenance (4 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7426fc8081908a8227f73168c235 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:37 p.m.