Triple
T11910062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank station |
E283368
|
entity |
| Predicate | hasAccess |
P273
|
FINISHED |
| Object | Bank junction |
E69095
|
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: Bank junction | Statement: [Bank station, hasAccess, Bank junction]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bank junction Context triple: [Bank station, hasAccess, Bank junction]
-
A.
Bank junction
chosen
Bank junction is a major road intersection and financial hub in the City of London, surrounded by landmark institutions such as the Bank of England and the Royal Exchange.
-
B.
Bank
Bank is a major London Underground and rail interchange in the City of London, serving as a key hub for financial district commuters.
-
C.
Banks
Banks is a residential suburb in the Tuggeranong district of Canberra, Australian Capital Territory.
-
D.
Banks
Banks is a small village in Lancashire, England, known for its rural character and proximity to the town of Tarleton.
-
E.
Banks
Banks is a common English surname borne by numerous notable individuals across sports, politics, arts, and other fields.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f418543258819083b49a5bbdc520cd |
completed | May 1, 2026, 3:04 a.m. |
Created at: April 8, 2026, 9:44 p.m.