Triple
T2062963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Sign Language |
E45832
|
entity |
| Predicate | hasOwnMorphology |
P7162
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [British Sign Language, hasOwnMorphology, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnMorphology Context triple: [British Sign Language, hasOwnMorphology, yes]
-
A.
hasMorphologicalType
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
-
B.
modifiesMorphologyOf
Indicates that one entity alters or changes the morphological structure or form of another entity.
-
C.
hasLinguisticFeature
chosen
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
D.
hasSyllableStructure
Indicates that an entity (typically a word or morpheme) possesses a particular arrangement or pattern of syllables.
-
E.
hasLinguisticElement
Indicates that one entity includes, is associated with, or is characterized by a particular linguistic component such as a word, phrase, symbol, or other language element.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d239b48190a9f303446cbe3aa6 |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.