Triple
T8495892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batticaloa Tamil |
E201096
|
entity |
| Predicate | hasDistinctive |
P18160
|
FINISHED |
| Object | phonology |
—
|
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: phonology | Statement: [Batticaloa Tamil, hasDistinctive, phonology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctive Context triple: [Batticaloa Tamil, hasDistinctive, phonology]
-
A.
hasDistinctFeature
chosen
Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
-
B.
hasDistinction
Indicates that one entity possesses, is awarded, or is recognized with a special honor, title, or mark of excellence in relation to another entity or context.
-
C.
hasDistinctLetters
Indicates that all letters in the given string or word are unique, with no character repeated.
-
D.
hasRegisterDistinction
Indicates that there is a meaningful difference in language register (e.g., formality or style) between the related linguistic forms or usages.
-
E.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57dbe488190af5f06faf862cd5d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.