Triple
T1100923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Leyland |
E24377
|
entity |
| Predicate | familyName |
P18
|
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: [Jim Leyland, familyName, Leyland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leyland Context triple: [Jim Leyland, familyName, 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 small rural village located within the district of West Oxfordshire in Oxfordshire, England.
-
C.
Blackburn
Blackburn is a large industrial town in Lancashire, England, historically known for its textile manufacturing and located north of Manchester.
-
D.
Dudley
Dudley is a large industrial town in England’s West Midlands, historically known for its role in the Black Country and its prominent castle and zoo.
-
E.
Dudley
Dudley is a masculine given name of English origin that has been borne by various notable figures in literature, politics, and entertainment.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c079f48190a0e0ddda182f7a01 |
completed | March 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac4c47dbf88190a1898d7bda32ecb2 |
completed | March 7, 2026, 4:03 p.m. |
Created at: March 1, 2026, 7:43 p.m.