Triple
T36394774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aabenraa Church |
E896440
|
entity |
| Predicate | locatedInOldCulturalRegion |
P88079
|
FINISHED |
| Object | Southern Jutland |
E176942
|
NE 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: Southern Jutland | Statement: [Aabenraa Church, locatedInOldCulturalRegion, Southern Jutland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInOldCulturalRegion Context triple: [Aabenraa Church, locatedInOldCulturalRegion, Southern Jutland]
-
A.
locatedInModernAdministrativeRegion
Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
-
B.
locatedInTraditionalRegion
chosen
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
C.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
D.
earlierCulturalSphere
Indicates that one cultural sphere existed or was influential before another in time.
-
E.
isCulturalAreaFor
Indicates that one entity serves as a designated cultural area or space intended for the cultural activities, practices, or identity of another entity.
- F. None of above.
Provenance (4 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfbf477c8190a3338e655514dfaa |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.