Triple
T8992711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caspian languages |
E214827
|
entity |
| Predicate | areDistinguishedFrom |
P1612
|
FINISHED |
| Object | Southwestern Iranian languages |
—
|
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: Southwestern Iranian languages | Statement: [Caspian languages, areDistinguishedFrom, Southwestern Iranian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areDistinguishedFrom Context triple: [Caspian languages, areDistinguishedFrom, Southwestern Iranian languages]
-
A.
isDistinctFrom
chosen
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
B.
categoryDistinguishedFrom
Indicates that one category is explicitly distinguished from another, clarifying that they are separate and should not be confused.
-
C.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
D.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
E.
differentiatedFrom
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6876583081909d936dc3c3152587 |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.