Triple
T58310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Society |
E1154
|
entity |
| Predicate | headquartersCity |
P62
|
FINISHED |
| Object | London |
E1817
|
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: London | Statement: [Royal Society, headquartersCity, London]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: London Context triple: [Royal Society, headquartersCity, London]
-
A.
London, England
chosen
London, England is the capital and largest city of the United Kingdom, renowned as a global center for finance, culture, and politics.
-
B.
City of London
The City of London is the historic and financial core of Greater London, renowned as one of the world’s leading global finance and business centers.
-
C.
Liverpool
Liverpool is a major port city in northwest England known for its maritime heritage, cultural influence, and role as the birthplace of The Beatles.
-
D.
Bristol
Bristol is a historic port city in southwest England known for its maritime heritage, vibrant cultural scene, and distinctive Georgian and Victorian architecture.
-
E.
Lexington, England
Lexington, England is a historic English locality whose name was later adopted by the American town of Lexington, Massachusetts.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b1d133c819098a2f2447bbd9339 |
completed | Feb. 28, 2026, 1:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a33e3a315881909a2b717ef20e4b17 |
completed | Feb. 28, 2026, 7:12 p.m. |
Created at: Feb. 28, 2026, 1:50 a.m.