Triple
T19639902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordillera de la Sal |
E471501
|
entity |
| Predicate | usedAsAnalogueFor |
P3882
|
FINISHED |
| Object | Martian landscapes |
—
|
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: Martian landscapes | Statement: [Cordillera de la Sal, usedAsAnalogueFor, Martian landscapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsAnalogueFor Context triple: [Cordillera de la Sal, usedAsAnalogueFor, Martian landscapes]
-
A.
usedAsAnalogFor
chosen
Indicates that one entity is employed as a comparison or illustrative counterpart to help explain, represent, or understand another entity.
-
B.
alternativeUsedBy
Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
-
C.
relatedAnalogy
Indicates that one entity is connected to another through an analogy, expressing a similarity or correspondence in structure, function, or relationship between them.
-
D.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
E.
isAlsoUsedAs
Indicates that something serves an additional function or role beyond its primary one.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641215df48190926b38e6502bb83e |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.