Triple
T18695739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier (lunar crater) |
E457109
|
entity |
| Predicate | elongationDirection |
P15748
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [Messier (lunar crater), elongationDirection, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elongationDirection Context triple: [Messier (lunar crater), elongationDirection, east–west]
-
A.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
B.
isElongatedDueTo
Indicates that one entity becomes longer in shape, form, or duration specifically as a result of the influence or effect of another entity or factor.
-
C.
offsetDirection
chosen
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
D.
peakDirectionExpress
Indicates the direction in which a peak (such as a maximum value or intensity) is oriented or expressed.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.