Triple
T16183990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rote Insel |
E392751
|
entity |
| Predicate | borderedByInfrastructure |
P111735
|
FINISHED |
| Object | railway lines |
—
|
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: railway lines | Statement: [Rote Insel, borderedByInfrastructure, railway lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByInfrastructure Context triple: [Rote Insel, borderedByInfrastructure, railway lines]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
intersectsInfrastructure
chosen
Indicates that one entity crosses, overlaps with, or physically intersects an infrastructure element (such as a road, pipeline, or utility line).
-
C.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
D.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
E.
hasBorderFacilities
Indicates that one entity possesses or is equipped with facilities or infrastructure used for managing or servicing a border with 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205fc080819097858f36253fef7c |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.