Triple
T28584608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okrąglica summit |
E723457
|
entity |
| Predicate | isMostFamousPeakOf |
P165760
|
FINISHED |
| Object | Trzy Korony massif |
—
|
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: Trzy Korony massif | Statement: [Okrąglica summit, isMostFamousPeakOf, Trzy Korony massif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMostFamousPeakOf Context triple: [Okrąglica summit, isMostFamousPeakOf, Trzy Korony massif]
-
A.
nearHighestPeakOf
Indicates that one entity is located close to the highest peak of another referenced geographic or topographic feature.
-
B.
isOneOfHighestPeaksIn
Indicates that an entity is among the tallest or most elevated peaks within a specified group, region, or category.
-
C.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
D.
hasHighestPeakName
Indicates that the related value is the name of the tallest peak associated with the given entity.
-
E.
isMostTopographicallyProminentIn
Indicates that an entity has the greatest topographic prominence within a specified area or group, exceeding that of all comparable entities.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 28, 2026, 4:16 a.m.