Triple
T468440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh Waverley |
E8500
|
entity |
| Predicate | hasServiceTo |
P6787
|
FINISHED |
| Object | Inverness |
E50911
|
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: Inverness | Statement: [Edinburgh Waverley, hasServiceTo, Inverness]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inverness Context triple: [Edinburgh Waverley, hasServiceTo, Inverness]
-
A.
Inverness
chosen
Inverness is a city in the Scottish Highlands that serves as a major cultural and administrative center for the region.
-
B.
Greenock
Greenock is a historic port town and former shipbuilding center on the River Clyde in western Scotland.
-
C.
Aberdeen
Aberdeen is a major port city in northeast Scotland known for its North Sea oil industry, granite architecture, and role as a regional economic and cultural hub.
-
D.
Dundee
Dundee is a coastal city in eastern Scotland known for its historic jute industry, maritime heritage, and contemporary cultural and design scene.
-
E.
Stirling
Stirling is a historic Scottish city known for its medieval castle, strategic location, and role in key battles such as Stirling Bridge and Bannockburn.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd9bea081909ee782840f3da12b |
completed | Feb. 28, 2026, 1:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a654ced04c819083e3cf2e44079341 |
completed | March 3, 2026, 3:26 a.m. |
Created at: Feb. 28, 2026, 1:12 p.m.