Triple
T9516143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera Rubin Ridge |
E229529
|
entity |
| Predicate | hasTopographicExpression |
P87992
|
FINISHED |
| Object | prominent ridge |
—
|
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: prominent ridge | Statement: [Vera Rubin Ridge, hasTopographicExpression, prominent ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopographicExpression Context triple: [Vera Rubin Ridge, hasTopographicExpression, prominent ridge]
-
A.
hasTopographicContext
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
B.
hasTopographicalRole
Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
-
C.
associatedTopography
chosen
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
D.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
E.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd987eefec8190b0db1928776bf02b |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.