Triple
T7408841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odysseus impact basin |
E170947
|
entity |
| Predicate | surfaceRelaxation |
P76597
|
FINISHED |
| Object | viscous relaxation of ice |
—
|
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: viscous relaxation of ice | Statement: [Odysseus impact basin, surfaceRelaxation, viscous relaxation of ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceRelaxation Context triple: [Odysseus impact basin, surfaceRelaxation, viscous relaxation of ice]
-
A.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
-
B.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
C.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
D.
surfaceQuality
Indicates the condition or characteristics of an entity’s outer surface, such as its smoothness, roughness, or finish.
-
E.
surfaceOperation
Indicates an operation or activity that is performed on or at the surface of an object, material, or environment.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c6f15c36d48190bc75353d3f67555a |
completed | March 27, 2026, 9:06 p.m. |
Created at: March 27, 2026, 3:10 p.m.