Triple
T31548312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Manchester |
E804925
|
entity |
| Predicate | hasLordMayor |
P194997
|
FINISHED |
| Object | Lord Mayor of Manchester |
E4165
|
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: Lord Mayor of Manchester | Statement: [City of Manchester, hasLordMayor, Lord Mayor of Manchester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLordMayor Context triple: [City of Manchester, hasLordMayor, Lord Mayor of Manchester]
-
A.
hasMayor
Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
-
B.
hasLordSpeaker
Indicates that one entity serves as the Lord Speaker (presiding officer) of another entity, typically a parliamentary or legislative body.
-
C.
hasCeremonialLordLieutenant
Indicates that an administrative area is formally assigned a specific ceremonial lord-lieutenant as its official representative.
-
D.
cityMayor
Indicates that one entity serves as the mayor (chief elected municipal official) of the city represented by the other entity.
-
E.
hasHeadOfLocalGovernment
Indicates that an administrative area is associated with the person who serves as its chief local government official.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d8eeff08190bb1372f652ba490e |
completed | June 11, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: April 30, 2026, 10:09 p.m.