Triple
T17685070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MR3 highway |
E440866
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | MR3 |
—
|
NE NERFINISHED |
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: MR3 | Statement: [MR3 highway, hasAbbreviation, MR3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MR3 Context triple: [MR3 highway, hasAbbreviation, MR3]
-
A.
MR3
chosen
MR3 is a designated route number for a specific regional highway.
-
B.
MR2
MR2 is a variant designation used for the British Royal Air Force’s Nimrod maritime patrol aircraft, indicating its second major production and upgrade version.
-
C.
M3
M3 is a major motorway in the United Kingdom that connects London to Southampton, serving as a key route through southern England.
-
D.
M3
M3 is a NASA-designed imaging spectrometer that flew on India's Chandrayaan-1 lunar mission to map the Moon’s surface mineralogy and detect water and hydroxyl signatures.
-
E.
M3
M3 is the third line of the Milan Metro system, running in a north–south direction and serving key areas of Milan, Italy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704710488190826aaf0bdd4b2088 |
completed | April 19, 2026, 6:03 a.m. |
Created at: April 10, 2026, 10:02 a.m.