Triple
T35089684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Siple |
E1012682
|
entity |
| Predicate | risesAbove |
P133850
|
FINISHED |
| Object | Ross Sea |
—
|
NE NERFINISHED |
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: Ross Sea | Statement: [Mount Siple, risesAbove, Ross Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: risesAbove Context triple: [Mount Siple, risesAbove, Ross Sea]
-
A.
risesIn
Indicates that a river or similar watercourse originates or begins its flow in a specified location.
-
B.
risesOn
Indicates that one entity ascends, increases, or moves upward in position, level, or value relative to another reference point or context.
-
C.
isElevatedAbove
chosen
Indicates that one entity is positioned at a higher vertical level or altitude than another entity.
-
D.
wasAbove
Indicates that one entity was positioned at a higher vertical level than another entity at some point in time.
-
E.
risesSteeplyFrom
Indicates that one entity ascends sharply or abruptly upward starting from the position or level of 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.