Triple
T8848251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaplygin crater |
E210563
|
entity |
| Predicate | floorCondition |
P50429
|
FINISHED |
| Object | relatively level in places |
—
|
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: relatively level in places | Statement: [Chaplygin crater, floorCondition, relatively level in places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floorCondition Context triple: [Chaplygin crater, floorCondition, relatively level in places]
-
A.
floorType
Indicates the type or material classification of a floor associated with an entity.
-
B.
floorCharacteristic
chosen
Indicates that a specified characteristic or property is attributed to a floor or flooring surface.
-
C.
floor
Indicates that one entity is located on or forms the walking surface (the floor) beneath another entity within a space.
-
D.
floorConfiguration
Indicates how the layout, structure, or arrangement of floors or levels is organized or configured in relation to one another.
-
E.
floorAbove
Indicates that one floor is located directly above another floor in a vertical arrangement.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60aa6db0819097c3257499200afc |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.