Triple
T27135741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tornedalen culture |
E681680
|
entity |
| Predicate | hasBorderRegionCharacter |
P160921
|
FINISHED |
| Object | cross-border culture |
—
|
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: cross-border culture | Statement: [Tornedalen culture, hasBorderRegionCharacter, cross-border culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderRegionCharacter Context triple: [Tornedalen culture, hasBorderRegionCharacter, cross-border culture]
-
A.
hasBorderAreaCharacteristics
chosen
Indicates that something possesses features or qualities typical of a border area between regions or territories.
-
B.
hasBorderLengthCharacteristic
Indicates that a border is associated with a specific length-related property or characteristic.
-
C.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
D.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
-
E.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 9:07 a.m.