Triple
T9684233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh to Aberdeen line |
E234363
|
entity |
| Predicate | viaTown |
P83398
|
FINISHED |
| Object | Montrose |
E27714
|
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: Montrose | Statement: [Edinburgh to Aberdeen line, viaTown, Montrose]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Montrose Context triple: [Edinburgh to Aberdeen line, viaTown, Montrose]
-
A.
Montrose
Montrose is a city in western Colorado known for its access to outdoor recreation, including nearby national parks and scenic mountain landscapes.
-
B.
Montrose
Montrose is a residential neighborhood within the town of Wakefield in Middlesex County, Massachusetts.
-
C.
Montrose
chosen
Montrose is a coastal town in eastern Scotland known for its historic harbor, sandy beach, and surrounding nature reserves.
-
D.
Montrose
Montrose is a vibrant, artsy neighborhood in Houston, Texas, known for its eclectic culture, historic homes, and diverse community.
-
E.
Montrose
Montrose is a small town located in Dane County in the state of Wisconsin, United States.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ccf21a08190a1302b933b9e50be |
completed | April 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19106e67881909505287620d2f781 |
completed | April 4, 2026, 10:30 p.m. |
Created at: March 30, 2026, 8:16 p.m.