Triple
T34308535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Камен мост |
E880377
|
entity |
| Predicate | разположенНадморскаВисочина |
P45909
|
FINISHED |
| Object | приблизително 245 m |
—
|
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: приблизително 245 m | Statement: [Камен мост, разположенНадморскаВисочина, приблизително 245 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: разположенНадморскаВисочина Context triple: [Камен мост, разположенНадморскаВисочина, приблизително 245 m]
-
A.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
-
B.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
C.
elevationApproxMeters
chosen
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
D.
elevationAboveSurroundingPlains
Indicates that something is situated at a higher altitude than the nearby flat or low-lying surrounding plains.
-
E.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:57 a.m.