Triple
T38296907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skala |
E1032112
|
entity |
| Predicate | relativePositionOnOlympus |
P44470
|
FINISHED |
| Object | one of the main summits |
—
|
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: one of the main summits | Statement: [Skala, relativePositionOnOlympus, one of the main summits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionOnOlympus Context triple: [Skala, relativePositionOnOlympus, one of the main summits]
-
A.
positionOnPerseverance
Indicates that one entity occupies a specific physical location or mounting point on the Perseverance rover.
-
B.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
C.
locatedOnPlateauBetween
Indicates that one entity is situated on a plateau that lies between two other referenced geographic or spatial entities.
-
D.
relativeLocationToDenali
Indicates the spatial position or orientation of something in relation to Denali’s location.
-
E.
targetRegionOnMars
Indicates that an entity designates or is associated with a specific geographic region located on the planet Mars.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.