Triple
T30941138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eggegebirge |
E788262
|
entity |
| Predicate | runsThroughDistrict |
P45427
|
FINISHED |
| Object | Paderborn district |
—
|
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: Paderborn district | Statement: [Eggegebirge, runsThroughDistrict, Paderborn district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsThroughDistrict Context triple: [Eggegebirge, runsThroughDistrict, Paderborn district]
-
A.
ranForDistrict
Indicates that an individual was a candidate running for election to represent a specific district.
-
B.
passesThroughDistrict
chosen
Indicates that something (such as a route, boundary, or path) traverses or goes through a particular district.
-
C.
runsThroughNeighborhood
Indicates that something (such as a route, path, or service) passes through or traverses a particular neighborhood.
-
D.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
E.
urbanDistrictsTraversed
Indicates that a route, path, or entity passes through or crosses one or more urban districts.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6930fe7a48190b5cec6c1bc4627b6 |
completed | May 3, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:53 p.m.