Triple
T38188787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Manchester |
E1005393
|
entity |
| Predicate | hasMainLondonCity |
P207632
|
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: [London–Manchester, hasMainLondonCity, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLondonCity Context triple: [London–Manchester, hasMainLondonCity, London]
-
A.
hasLondonBorough
Indicates that an entity includes, contains, or is associated with a specific London borough as one of its administrative subdivisions.
-
B.
hasOuterLondonBorough
Indicates that an entity is associated with, located in, or administered by a borough that is part of Outer London.
-
C.
isInLondonSubRegion
Indicates that one entity is located within the London sub-region of another defined geographic or administrative area.
-
D.
isInInnerLondon
Indicates that one location lies within the administrative area defined as Inner London.
-
E.
isOuterLondonBorough
Indicates that a borough is classified as part of Outer London rather than Inner London.
- F. None of above. chosen
Provenance (5 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a418533a08481909bfab2a319aa8c99 |
completed | June 28, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:29 p.m.