Triple
T9478013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auslan |
E228563
|
entity |
| Predicate | languageFamily |
P1047
|
FINISHED |
| Object | BANZSL |
E45831
|
NE 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: BANZSL | Statement: [Auslan, languageFamily, BANZSL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BANZSL Context triple: [Auslan, languageFamily, BANZSL]
-
A.
BANZSL
chosen
BANZSL is the family of closely related sign languages used in Britain, Australia, and New Zealand, sharing a common historical origin and many linguistic features.
-
B.
BZN
BZN is a Dutch pop band best known for its melodic, easy-listening songs and long-standing popularity in the Netherlands.
-
C.
BZ
BZ is the two-letter ISO 3166-1 alpha-2 country code assigned to Belize.
-
D.
BZ
BZ is the commonly used abbreviation for the Ministry of Foreign Affairs of the Netherlands, which is responsible for the country’s foreign policy and international relations.
-
E.
BZ
BZ is the vehicle registration code used on license plates for the municipality of Rammenau in Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd801386948190890133f622ff360b |
completed | April 1, 2026, 8:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d139f261248190b8e3238f7618191d |
completed | April 4, 2026, 4:18 p.m. |
Created at: March 30, 2026, 7:54 p.m.