Triple
T28121568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Mountain |
E710805
|
entity |
| Predicate | highestKnownPeakNear |
P101565
|
FINISHED |
| Object | Arendelle |
—
|
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: Arendelle | Statement: [North Mountain, highestKnownPeakNear, Arendelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestKnownPeakNear Context triple: [North Mountain, highestKnownPeakNear, Arendelle]
-
A.
highestNearbyPeakElevationInFeet
Indicates the elevation in feet of the tallest peak located within a defined nearby area of a given reference point.
-
B.
nearbySummit
chosen
Indicates that one summit is located close to another summit in geographic space.
-
C.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
D.
highestPeaksLocatedIn
Indicates that the specified highest mountain peaks are geographically situated within the given location or region.
-
E.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 9:17 p.m.