Triple
T891271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Borough of Harrow |
E19242
|
entity |
| Predicate | timeZoneDST |
P109
|
FINISHED |
| Object | BST |
E53598
|
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: BST | Statement: [London Borough of Harrow, timeZoneDST, BST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BST Context triple: [London Borough of Harrow, timeZoneDST, BST]
-
A.
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.
-
B.
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.
-
C.
Stanford Tree
The Stanford Tree is the unofficial, whimsical and often irreverent costumed mascot of Stanford University’s marching band, known for its ever-changing, student-designed tree costume.
-
D.
BSTJ
BSTJ is the commonly used abbreviation for the Bell System Technical Journal, a renowned scientific and engineering journal published by Bell Labs.
-
E.
GiST
GiST (Generalized Search Tree) is a flexible indexing framework in PostgreSQL that allows the implementation of a wide variety of custom index types for complex data and queries.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad019e448190ab991e85dc6d7708 |
completed | March 1, 2026, 9:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7c025464081908032939637248635 |
completed | March 4, 2026, 5:16 a.m. |
Created at: March 1, 2026, 7:39 p.m.