Triple
T28461297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kočevje |
E720160
|
entity |
| Predicate | hasNearbyEthnographicRegion |
P74006
|
FINISHED |
| Object | Gottschee region |
—
|
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: Gottschee region | Statement: [Kočevje, hasNearbyEthnographicRegion, Gottschee region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyEthnographicRegion Context triple: [Kočevje, hasNearbyEthnographicRegion, Gottschee region]
-
A.
belongsToEthnographicRegion
chosen
Indicates that an entity is associated with or situated within a specific ethnographic region defined by shared cultural or ethnic characteristics.
-
B.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
C.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
D.
hasNearbyEconomicRegion
Indicates that one economic region is geographically close to or adjacent to another economic region.
-
E.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical area.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 28, 2026, 2:40 a.m.