Triple
T27291340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Peak |
E688633
|
entity |
| Predicate | relativeToMountNebo |
P199721
|
FINISHED |
| Object | one of the principal summits of Mount Nebo |
—
|
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 principal summits of Mount Nebo | Statement: [South Peak, relativeToMountNebo, one of the principal summits of Mount Nebo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToMountNebo Context triple: [South Peak, relativeToMountNebo, one of the principal summits of Mount Nebo]
-
A.
mountOf
Indicates that one entity serves as the mount or riding animal/creature used by another entity.
-
B.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
C.
positionRelativeToChesed
Indicates the spatial or conceptual position of something in relation to Chesed.
-
D.
positionRelativeToDeity
Indicates the spatial or hierarchical position an entity holds in relation to a specified deity.
-
E.
relativeLocationToNaikū
Indicates the spatial relationship or position of something in relation to Naikū.
- F. None of above. chosen
Provenance (4 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69ff528536d481909caefe52fcd8aaa7 |
completed | May 9, 2026, 3:28 p.m. |
Created at: April 27, 2026, 11:15 a.m.