Triple
T7490182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B676 road |
E176984
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Rutland |
E86840
|
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: Rutland | Statement: [B676 road, locatedIn, Rutland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rutland Context triple: [B676 road, locatedIn, Rutland]
-
A.
Rutland
chosen
Rutland is a small historic county in the East Midlands of England, known for its rural character and Rutland Water reservoir.
-
B.
Rutland
Rutland is an unincorporated community located in Bibb County, Georgia, United States.
-
C.
Rutland
Rutland is a small city in central Vermont known historically as a marble quarrying center and as a regional hub for commerce and outdoor recreation.
-
D.
Rutland
Rutland is a small town in Worcester County, Massachusetts, known for its rural character and location near the geographic center of the state.
-
E.
Berkshire
Berkshire is a historic county in South East England known for its royal connections, including Windsor Castle, and its mix of affluent towns and rural landscapes.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55bdb3481908653b46eafba011d |
completed | March 27, 2026, 9:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c83c71f5748190bdda4cf9b8dfc6ea |
completed | March 28, 2026, 8:39 p.m. |
Created at: March 27, 2026, 3:43 p.m.