Triple
T25367166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arewelian Hayeren |
E632830
|
entity |
| Predicate | hasSpokenInRegion |
P162518
|
FINISHED |
| Object | South Caucasus |
—
|
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: South Caucasus | Statement: [Arewelian Hayeren, hasSpokenInRegion, South Caucasus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenInRegion Context triple: [Arewelian Hayeren, hasSpokenInRegion, South Caucasus]
-
A.
spokenInState
Indicates that a language or dialect is spoken within the geographic or political boundaries of a particular state.
-
B.
spokenInNeighboringRegionsOf
Indicates that a language or speech variety is used in regions that geographically border the primary region associated with another language or entity.
-
C.
spokenOnContinent
Indicates that something, typically a language or speech, is used or occurs on a particular continent.
-
D.
spokenInPartOf
chosen
Indicates that a language or dialect is spoken within a specific subregion or part of a larger geographic or administrative area.
-
E.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:37 p.m.