Triple
T14644410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Street, Manchester |
E343808
|
entity |
| Predicate | hasPostcodeArea |
P920
|
FINISHED |
| Object | M2 |
E785840
|
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: M2 | Statement: [Portland Street, Manchester, hasPostcodeArea, M2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M2 Context triple: [Portland Street, Manchester, hasPostcodeArea, M2]
-
A.
M2
M2 is a major British motorway that connects London with the port town of Dover in Kent, serving as an important route to the Channel ports.
-
B.
M2
M2 was the original name of MTV2, a U.S. cable television channel that focused on music videos and youth-oriented programming.
-
C.
M2
M2 is a boat line that operates as part of Geneva’s public transport network, providing passenger services across the city’s waters.
-
D.
M2
chosen
M2 is a central Manchester, England postcode district covering part of the city’s main commercial and business area.
-
E.
M2
M2 is a major motorway in Northern Ireland that forms part of the key route connecting Belfast with the northern part of the country.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ea6d8481908e6331ca173c646b |
completed | April 14, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5d5d05481908dbb23392c05d23b |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:26 a.m.