Triple
T7408880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ithaca Chasma |
E170948
|
entity |
| Predicate | featureTypeDesignation |
P5048
|
FINISHED |
| Object | chasma |
—
|
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: chasma | Statement: [Ithaca Chasma, featureTypeDesignation, chasma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureTypeDesignation Context triple: [Ithaca Chasma, featureTypeDesignation, chasma]
-
A.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
C.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
D.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f29acf588190a7c4056bdc4f3ffc |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.