Triple
T30523694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RK |
E776770
|
entity |
| Predicate | geographicalAreaCovered |
P19200
|
FINISHED |
| Object | city of Krosno and surrounding area |
—
|
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: city of Krosno and surrounding area | Statement: [RK, geographicalAreaCovered, city of Krosno and surrounding area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalAreaCovered Context triple: [RK, geographicalAreaCovered, city of Krosno and surrounding area]
-
A.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
-
B.
geographicCoverageType
Indicates the type or nature of the geographic area that something covers or applies to.
-
C.
territoriesCovered
Indicates that one entity includes, spans, or encompasses the geographic or jurisdictional areas associated with another entity.
-
D.
regionCoverage
chosen
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
E.
containsGeographicalArea
Indicates that one geographical area spatially encompasses or includes another geographical area within its boundaries.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 8:17 p.m.