Triple
T36463476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main-Rhön |
E898360
|
entity |
| Predicate | belongsToPlanningSystem |
P63005
|
FINISHED |
| Object | Bavarian regional planning system |
—
|
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: Bavarian regional planning system | Statement: [Main-Rhön, belongsToPlanningSystem, Bavarian regional planning system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToPlanningSystem Context triple: [Main-Rhön, belongsToPlanningSystem, Bavarian regional planning system]
-
A.
hasPlanningAssociation
chosen
Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
-
B.
usedPlanningSystem
Indicates that an entity employed a particular planning system or methodology to carry out its planning activities.
-
C.
planningSystem
Indicates that an entity functions as or is associated with a system responsible for organizing, scheduling, or coordinating plans or activities.
-
D.
belongsToAdministrativeSystem
Indicates that one entity is part of, or under the jurisdiction of, a particular administrative system or framework.
-
E.
hasRelatedPlan
Indicates that one entity is associated with another entity through a plan that is relevant or connected to it.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 3, 2026, 4:10 p.m.