Triple
T15142936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lido |
E361731
|
entity |
| Predicate | hasCollaboratedWith |
P8554
|
FINISHED |
| Object | Banks |
E127732
|
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: Banks | Statement: [Lido, hasCollaboratedWith, Banks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Banks Context triple: [Lido, hasCollaboratedWith, Banks]
-
A.
Banks
Banks is a small village in Lancashire, England, known for its rural character and proximity to the town of Tarleton.
-
B.
Banks
chosen
Banks is a common English surname borne by numerous notable individuals across sports, politics, arts, and other fields.
-
C.
Banks
Banks is a residential suburb in the Tuggeranong district of Canberra, Australian Capital Territory.
-
D.
Bank
Bank is a major London Underground and rail interchange in the City of London, serving as a key hub for financial district commuters.
-
E.
Bank (financial institution)
A bank is a financial institution that accepts deposits, provides loans, and offers various financial services to individuals, businesses, and governments.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c5c4248190b57234e3ccf2831b |
completed | April 15, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69febfee0ae48190a36523d3eeae9740 |
completed | May 9, 2026, 5:02 a.m. |
Created at: April 10, 2026, 3:07 a.m.