Triple
T375448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry III of England |
E8362
|
entity |
| Predicate | deathPlace |
P21
|
FINISHED |
| Object | London, England |
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, England | Statement: [Henry III of England, deathPlace, London, England]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: London, England Context triple: [Henry III of England, deathPlace, London, England]
-
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.
London Victoria
London Victoria is a major central London railway terminus and Underground station, serving as a key hub for commuter, regional, and Gatwick Airport services.
-
C.
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.
-
D.
Middlesex, England
Middlesex, England is a historic county in southeast England that once encompassed much of what is now Greater London.
-
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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec1585648190943f1c698e9b2d81 |
completed | Feb. 28, 2026, 1:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a49eb45f188190a6e1b6d341b29f2a |
completed | March 1, 2026, 8:16 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.