Triple
T32769441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasovskiy crater |
E838005
|
entity |
| Predicate | hasRelativeCondition |
P1255
|
FINISHED |
| Object | moderately eroded |
—
|
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: moderately eroded | Statement: [Krasovskiy crater, hasRelativeCondition, moderately eroded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeCondition Context triple: [Krasovskiy crater, hasRelativeCondition, moderately eroded]
-
A.
relativeCondition
Indicates that one entity’s condition, state, or status is defined or evaluated in relation to another entity’s condition, state, or status.
-
B.
hasCondition
chosen
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
C.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
D.
hasChainCondition
Indicates that one entity is subject to, or satisfies, a specified chain condition imposed or characterized by another entity.
-
E.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a030f1480148190a5e8c8926ded252c |
completed | May 12, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_6a030e7f5fa481909696733defefcc20 |
completed | May 12, 2026, 11:26 a.m. |
Created at: May 1, 2026, 1:13 a.m.