Triple
T27425996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinsberg |
E690485
|
entity |
| Predicate | partOfEuroRegion |
P106493
|
FINISHED |
| Object | Euregio Maas-Rhein |
—
|
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: Euregio Maas-Rhein | Statement: [Heinsberg, partOfEuroRegion, Euregio Maas-Rhein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfEuroRegion Context triple: [Heinsberg, partOfEuroRegion, Euregio Maas-Rhein]
-
A.
europeanUnionRegion
Indicates that an entity is located in, associated with, or falls under the jurisdiction of a region defined by or within the European Union.
-
B.
hasEuroregion
chosen
Indicates a relationship where a geographic or administrative entity is part of, or associated with, a specific Euroregion.
-
C.
europeanRegion
Indicates that an entity is located in, associated with, or classified as part of a region within Europe.
-
D.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
E.
belongsToEURegionType
Indicates that an entity is classified within a specific type or category of European Union region.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 27, 2026, 12:40 p.m.