Triple
T9478223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BSL |
E228567
|
entity |
| Predicate | usesNotationSystem |
P6517
|
FINISHED |
| Object |
HamNoSys
HamNoSys is a phonetic-style notation system designed to represent the precise articulation of sign languages in a written, language-independent form.
|
E802696
|
NE FINISHED |
How this triple was built (4 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: HamNoSys | Statement: [BSL, usesNotationSystem, HamNoSys]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HamNoSys Context triple: [BSL, usesNotationSystem, HamNoSys]
-
A.
Ham
Ham is a small town in the Somme department of northern France, known historically for its medieval fortress and strategic location.
-
B.
Ham
Ham is a municipality in the Belgian province of Limburg, known for its rural character and location in the Flemish Region.
-
C.
Ham
Ham is a suburban riverside district in southwest London, England, known for its historic houses, green spaces, and proximity to the River Thames.
-
D.
Ham
Ham is a biblical figure known as one of Noah’s sons and a progenitor of several ancient peoples mentioned in the Hebrew Bible.
-
E.
HAM
HAM is the IATA airport code for Hamburg Airport, the international airport serving the city of Hamburg, Germany.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: HamNoSys Triple: [BSL, usesNotationSystem, HamNoSys]
Generated description
HamNoSys is a phonetic-style notation system designed to represent the precise articulation of sign languages in a written, language-independent form.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: HamNoSys Target entity description: HamNoSys is a phonetic-style notation system designed to represent the precise articulation of sign languages in a written, language-independent form.
-
A.
Ham
Ham is a small town in the Somme department of northern France, known historically for its medieval fortress and strategic location.
-
B.
Ham
Ham is a suburban riverside district in southwest London, England, known for its historic houses, green spaces, and proximity to the River Thames.
-
C.
Ham
Ham is a biblical figure known as one of Noah’s sons and a progenitor of several ancient peoples mentioned in the Hebrew Bible.
-
D.
Ham
Ham is a municipality in the Belgian province of Limburg, known for its rural character and location in the Flemish Region.
-
E.
HAM
HAM is the IATA airport code for Hamburg Airport, the international airport serving the city of Hamburg, Germany.
- F. None of above. chosen
Provenance (5 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd8014fd0c819093bd15816f3db357 |
completed | April 1, 2026, 8:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12cf057908190a0541f0fed4ffd13 |
completed | April 4, 2026, 3:23 p.m. |
| NEDg | Description generation | batch_69d130d9e9c08190866ac7ca6a7960aa |
completed | April 4, 2026, 3:40 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d131268cd881909b3666bc20442405 |
completed | April 4, 2026, 3:41 p.m. |
Created at: March 30, 2026, 7:54 p.m.