Triple
T9791706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruneian |
E237620
|
entity |
| Predicate | associatedWithInternetTLD |
P248
|
FINISHED |
| Object | .bn |
E75322
|
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: .bn | Statement: [Bruneian, associatedWithInternetTLD, .bn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: .bn Context triple: [Bruneian, associatedWithInternetTLD, .bn]
-
A.
.bn
chosen
.bn is the country code top-level domain (ccTLD) assigned to Brunei Darussalam for use in its internet addresses.
-
B.
BNNS
BNNS (Basic Neural Network Subroutines) is Apple’s low-level, hardware-accelerated framework for performing neural network and machine learning computations efficiently on Apple devices.
-
C.
BN
BN is the vehicle registration code used on license plates for the German city of Bonn.
-
D.
BN2
BN2 is a UK postal district covering parts of eastern Brighton and nearby areas within the BN (Brighton) postcode region.
-
E.
BN3
BN3 is a UK postal district covering the Hove area and parts of Brighton in East Sussex.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda3456bac819097afb20ce9081dd7 |
completed | April 1, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c43141cc81908c45a3f5d5103564 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:28 p.m.