Triple
T13601628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek–Albanian border |
E324954
|
entity |
| Predicate | languageInBorderArea |
P77518
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [Greek–Albanian border, languageInBorderArea, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageInBorderArea Context triple: [Greek–Albanian border, languageInBorderArea, Greek]
-
A.
languageAlongBorder
chosen
Indicates that a particular language is spoken or prevalent along the border between two regions or entities.
-
B.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
C.
languageBorderInvolved
Indicates that a situation, event, or relationship involves or is affected by a boundary between different languages or linguistic communities.
-
D.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
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.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07ad3f48190a2173e42c5cfedb1 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.