Triple
T27934824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Hebe Crater |
E708075
|
entity |
| Predicate | relationshipToNearbyFeature |
P75079
|
FINISHED |
| Object | adjacent to Ubehebe Crater |
—
|
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: adjacent to Ubehebe Crater | Statement: [Little Hebe Crater, relationshipToNearbyFeature, adjacent to Ubehebe Crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToNearbyFeature Context triple: [Little Hebe Crater, relationshipToNearbyFeature, adjacent to Ubehebe Crater]
-
A.
nearbyFeature
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
B.
hasNeighborRelationshipWith
chosen
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
C.
spatialRelation
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
-
D.
relationshipToUsnavi
Indicates the type or nature of the relationship that an entity has with Usnavi.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: April 27, 2026, 7:05 p.m.