Triple
T11946129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banski Suhodol |
E284302
|
entity |
| Predicate | rankingByHeightInPirin |
P102406
|
FINISHED |
| Object | third highest peak in Pirin |
—
|
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: third highest peak in Pirin | Statement: [Banski Suhodol, rankingByHeightInPirin, third highest peak in Pirin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingByHeightInPirin Context triple: [Banski Suhodol, rankingByHeightInPirin, third highest peak in Pirin]
-
A.
rankOnMountAthos
Indicates the hierarchical or positional rank that an entity holds within the monastic or administrative structure on Mount Athos.
-
B.
rankByHeightWorld
Indicates an ordering of entities based on their relative height compared to all others in the world.
-
C.
rankingByLengthInAlps
Indicates an ordering of entities based on their relative lengths specifically within the context of the Alps.
-
D.
countryHighestPeaksRank
Indicates the relative ranking position of a country based on the heights of its highest peaks compared to those of other countries.
-
E.
regionRankByHeight
Indicates the relative ordering of regions based on their height or elevation.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903456ec0819082b8b10755a6b732 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.