Triple
T34285914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Struve (lunar crater) |
E879734
|
entity |
| Predicate | morphologicalState |
P112583
|
FINISHED |
| Object | eroded walls |
—
|
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: eroded walls | Statement: [Struve (lunar crater), morphologicalState, eroded walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: morphologicalState Context triple: [Struve (lunar crater), morphologicalState, eroded walls]
-
A.
hasMorphologicalState
chosen
Indicates that an entity possesses or is characterized by a particular morphological condition, form, or structural state.
-
B.
morphologicalRole
Indicates the specific functional role that a morphological element (such as an affix or morpheme) plays within the structure or formation of a word.
-
C.
morphologicalInterpretation
Indicates the specific morphological analysis or grammatical form assigned to an element (such as a word or morpheme) within a linguistic structure.
-
D.
morphologicalEvidence
Indicates that there is supporting evidence based on the form, structure, or morphology of the entities involved.
-
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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.