Triple
T28926508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serdi |
E733662
|
entity |
| Predicate | regionCrossedBy |
P416
|
FINISHED |
| Object | important Balkan routes |
—
|
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: important Balkan routes | Statement: [Serdi, regionCrossedBy, important Balkan routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCrossedBy Context triple: [Serdi, regionCrossedBy, important Balkan routes]
-
A.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
B.
crossedBy
chosen
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
C.
crossedBoundary
Indicates that an entity has moved from one defined area, region, or limit into another, thereby passing across a specified boundary.
-
D.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
E.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 8:23 a.m.