Triple
T24792290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbia–Bulgaria border |
E620281
|
entity |
| Predicate | crossesMountain |
P42201
|
FINISHED |
| Object | Balkan Mountains range |
—
|
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: Balkan Mountains range | Statement: [Serbia–Bulgaria border, crossesMountain, Balkan Mountains range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesMountain Context triple: [Serbia–Bulgaria border, crossesMountain, Balkan Mountains range]
-
A.
crossesMountainRange
Indicates that one entity traverses from one side of a mountain range to the other, passing through or over it.
-
B.
crossesMountainPass
Indicates that an entity traverses from one side of a mountain range to another via a defined mountain pass.
-
C.
crossesMountainRangeTo
chosen
Indicates that one entity traverses from one side of a mountain range to the other, passing across or through it as a route or connection.
-
D.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or entity.
-
E.
controlledMountainPasses
Indicates that an entity had authority over and could regulate access through specific mountain passes.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:47 a.m.