Triple
T26062818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Миджур |
E657311
|
entity |
| Predicate | найВисокВ |
P210
|
FINISHED |
| Object | сръбската част на Стара планина |
—
|
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: сръбската част на Стара планина | Statement: [Миджур, найВисокВ, сръбската част на Стара планина]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: найВисокВ Context triple: [Миджур, найВисокВ, сръбската част на Стара планина]
-
A.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
B.
formerHighest
Indicates that an entity once held the highest rank, position, or status in a given context but no longer does.
-
C.
tallestIn
Indicates that one entity has a greater height than all other relevant entities within a specified group or context.
-
D.
highestOrgan
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
-
E.
highestPoint
chosen
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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606941410819098a15b288273c3e1 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:20 p.m.