Triple
T15617715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setomaa region |
E375459
|
entity |
| Predicate | crossBorderCulturalRegion |
P55550
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Setomaa region, crossBorderCulturalRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderCulturalRegion Context triple: [Setomaa region, crossBorderCulturalRegion, true]
-
A.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
B.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderDialectOf
Indicates a dialect that is spoken in a border area and is linguistically associated with or derived from a particular neighboring language or dialect.
-
E.
crossBorderCommunity
chosen
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e980b748190b43c0b650bf1e629 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.