Triple
T16328313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Spanish Peak |
E396480
|
entity |
| Predicate | relativePositionToWestSpanishPeak |
P49440
|
FINISHED |
| Object | east |
—
|
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 | Statement: [East Spanish Peak, relativePositionToWestSpanishPeak, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionToWestSpanishPeak Context triple: [East Spanish Peak, relativePositionToWestSpanishPeak, east]
-
A.
positionRelativeToSummit
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
B.
hasRelativePositionOnCerroDeLaSilla
Indicates that one entity has a specific spatial or locational relationship relative to Cerro de la Silla.
-
C.
isEasternPeakOf
chosen
Indicates that one peak is the eastern member or counterpart within a set or pair of related peaks.
-
D.
prominenceRelativeToBatian
Indicates the degree to which something stands out or is elevated in comparison to Batian.
-
E.
hasRelativePositionToLicancabur
Indicates that one entity has a specific spatial or geographic position defined in relation to Licancabur.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dcd034819081d849003d918245 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.