Triple
T8648214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chirikof Point (islet) |
E205031
|
entity |
| Predicate | hasRegionalLanguageContext |
P8383
|
FINISHED |
| Object | Aleut |
—
|
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: Aleut | Statement: [Chirikof Point (islet), hasRegionalLanguageContext, Aleut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalLanguageContext Context triple: [Chirikof Point (islet), hasRegionalLanguageContext, Aleut]
-
A.
hasLanguageContext
chosen
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
-
B.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
C.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
D.
hasSuccessorLanguageInRegion
Indicates that one language is followed or replaced by another language within a specific geographic region.
-
E.
containsRegionalVocabulary
Indicates that the subject includes vocabulary items that are specific to a particular geographic region 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4812b7bc8190acb40da57cad293a |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.