Triple
T27110856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Peak |
E686706
|
entity |
| Predicate | relativeLocationToParent |
P23578
|
FINISHED |
| Object | north of Mount Nebo main summit |
—
|
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: north of Mount Nebo main summit | Statement: [North Peak, relativeLocationToParent, north of Mount Nebo main summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationToParent Context triple: [North Peak, relativeLocationToParent, north of Mount Nebo main summit]
-
A.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
B.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
C.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
elevationRelativeToParent
Indicates the vertical position or height of an entity relative to its parent entity’s elevation.
-
E.
positionHeldByParent
Indicates that a position or role is held by the parent of the referenced 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: April 27, 2026, 8:53 a.m.