Triple
T7408843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odysseus impact basin |
E170947
|
entity |
| Predicate | rimMorphology |
P10890
|
FINISHED |
| Object | low-relief rim |
—
|
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: low-relief rim | Statement: [Odysseus impact basin, rimMorphology, low-relief rim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rimMorphology Context triple: [Odysseus impact basin, rimMorphology, low-relief rim]
-
A.
notableMorphology
Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
-
B.
relatedMorphologicalFeature
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
-
C.
rimType
chosen
Indicates the specific style or configuration of a rim associated with an object or component.
-
D.
modifiesMorphologyOf
Indicates that one entity alters or changes the morphological structure or form of another entity.
-
E.
morphologicalClass
Indicates the classification of an entity based on its morphological form or structural pattern.
- 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.