Triple
T9489333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jia |
E228844
|
entity |
| Predicate | languageMode |
P6281
|
FINISHED |
| Object | sign language |
—
|
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 language | Statement: [Jia, languageMode, sign language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageMode Context triple: [Jia, languageMode, sign language]
-
A.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
B.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
C.
languageDesigned
Indicates that one entity created or developed the language used or associated with another entity.
-
D.
languageFeature
Indicates that one entity is a characteristic, property, or capability of a language associated with the other entity.
-
E.
languageForm
chosen
Indicates the specific linguistic form or expression in which something is conveyed or represented.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80c5a05c8190b97d34f010e60ca1 |
completed | April 1, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.