Triple
T20330340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stickney crater |
E492458
|
entity |
| Predicate | floorTopography |
P139728
|
FINISHED |
| Object | uneven and covered with smaller craters |
—
|
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: uneven and covered with smaller craters | Statement: [Stickney crater, floorTopography, uneven and covered with smaller craters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floorTopography Context triple: [Stickney crater, floorTopography, uneven and covered with smaller craters]
-
A.
floorHeight
Indicates the vertical elevation or level at which a particular floor is positioned within a structure.
-
B.
floorAbove
Indicates that one floor is located directly above another floor in a vertical arrangement.
-
C.
floorBelow
Indicates that one entity is located on the floor directly beneath another entity within the same structure.
-
D.
floor
Indicates that one entity is located on or forms the walking surface (the floor) beneath another entity within a space.
-
E.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e6f5d08190bedf376bbb999ebc |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:22 a.m.