Triple
T18727106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderby |
E457927
|
entity |
| Predicate | timeZoneDST |
P109
|
FINISHED |
| Object | BST |
—
|
NE NERFINISHED |
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: BST | Statement: [Enderby, timeZoneDST, BST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BST Context triple: [Enderby, timeZoneDST, BST]
-
A.
BST
BST is the time zone used throughout Bangladesh, set six hours ahead of Coordinated Universal Time (UTC+6).
-
B.
BST
chosen
BST (British Summer Time) is the daylight saving time observed in the United Kingdom, set one hour ahead of Coordinated Universal Time (UTC+1) during the summer months.
-
C.
AVL tree
An AVL tree is a self-balancing binary search tree data structure that maintains strict height balance to ensure efficient insertion, deletion, and lookup operations.
-
D.
B-tree
A B-tree is a self-balancing tree data structure that maintains sorted data and allows efficient insertion, deletion, and search operations, commonly used to implement database indexes.
-
E.
AVL
AVL is the three-letter IATA airport code for Asheville Regional Airport serving the Asheville, North Carolina area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d74bd9881908cd314e68327c402 |
completed | April 20, 2026, 12:04 a.m. |
Created at: April 10, 2026, 11:50 a.m.