Triple
T6795947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaconsfield, Buckinghamshire, England |
E156053
|
entity |
| Predicate | nearestMotorway |
P25934
|
FINISHED |
| Object | M40 |
E226183
|
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: M40 | Statement: [Beaconsfield, Buckinghamshire, England, nearestMotorway, M40]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M40 Context triple: [Beaconsfield, Buckinghamshire, England, nearestMotorway, M40]
-
A.
M40
chosen
M40 is a major British motorway linking London with Birmingham and the West Midlands.
-
B.
M-40
M-40 is a state trunkline highway in Michigan that runs north–south through several counties, including Allegan County.
-
C.
M45
M45 is the Pleiades, a prominent open star cluster in the constellation Taurus visible to the naked eye and known since antiquity.
-
D.
M4
M4 is a general-purpose macro processing language and preprocessor commonly used in Unix-like build systems and tools such as GNU Autoconf.
-
E.
M4
M4 is a boat line that operates as part of Geneva’s public transport network, providing passenger service across Lake Geneva.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2c6e7dc8190b1f33372d047baba |
completed | March 27, 2026, 6:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a9354448190890846c2e84bb22c |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:15 p.m.