Triple
T18564457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutton SignWriting block |
E453726
|
entity |
| Predicate | supportsLanguageType |
P45585
|
FINISHED |
| Object | sign 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: sign languages | Statement: [Sutton SignWriting block, supportsLanguageType, sign languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLanguageType Context triple: [Sutton SignWriting block, supportsLanguageType, sign languages]
-
A.
hasLanguageType
chosen
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
supportsExtensionLanguage
Indicates that one entity provides compatibility with or functionality for a specified extension language used by another entity.
-
D.
supportsLanguageOverrides
Indicates that an entity allows its default behavior or settings to be modified based on specific language selections or preferences.
-
E.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.