Triple
T11029617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish Sign Language |
E260722
|
entity |
| Predicate | hasManualAlphabet |
P26215
|
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: [Irish Sign Language, hasManualAlphabet, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManualAlphabet Context triple: [Irish Sign Language, hasManualAlphabet, yes]
-
A.
usesFingerspellingSystem
chosen
Indicates that one entity employs or applies a particular fingerspelling system in communication or representation.
-
B.
hasHandwritingOf
Indicates that one entity’s handwriting style or written text is attributed to, or produced by, another entity.
-
C.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
D.
hasBasicLetters
Indicates that an entity contains or is composed of fundamental alphabetic characters, without additional symbols or diacritics.
-
E.
hasOfficialWritingSystem
Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797d2feb881909a5684721e8b0d9c |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.