Triple
T10988237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main-Spessart |
E259685
|
entity |
| Predicate | hasRegionalKey |
P3446
|
FINISHED |
| Object | 09677 |
—
|
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: 09677 | Statement: [Main-Spessart, hasRegionalKey, 09677]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalKey Context triple: [Main-Spessart, hasRegionalKey, 09677]
-
A.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
B.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
C.
hasRegionalName
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
D.
hasDistrictKey
Indicates that an entity is associated with a specific district through a unique identifying key.
-
E.
hasRegionCode
chosen
Indicates that an entity is associated with a specific regional identifier or code.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b574d08190adec34b814a26437 |
completed | April 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.