Triple
T7810296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Commercial Vehicle Museum |
E180661
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Leyland |
E34365
|
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: Leyland | Statement: [British Commercial Vehicle Museum, locatedIn, Leyland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leyland Context triple: [British Commercial Vehicle Museum, locatedIn, Leyland]
-
A.
Leyland
chosen
Leyland is a town in Lancashire, England, historically known for its vehicle manufacturing industry, particularly Leyland Motors.
-
B.
Aston
Aston is a masculine given name of English origin, used both as a first name and a surname.
-
C.
Aston
Aston is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
-
D.
Blackburn
Blackburn is a large industrial town in Lancashire, England, historically known for its textile manufacturing and located north of Manchester.
-
E.
Blackburn
Blackburn is a small town in West Lothian, Scotland, known primarily as a residential community within the Central Belt.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78bb4b08190b2b3b51c5a0a033c |
completed | March 30, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb14651d488190b1bf6b875a2ebccd |
completed | March 31, 2026, 12:25 a.m. |
Created at: March 30, 2026, 4:37 p.m.