Triple
T19773293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertfordshire |
E474940
|
entity |
| Predicate | hasHistoricMarketTown |
P17485
|
FINISHED |
| Object | Royston |
—
|
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: Royston | Statement: [Hertfordshire, hasHistoricMarketTown, Royston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Royston Context triple: [Hertfordshire, hasHistoricMarketTown, Royston]
-
A.
Royston
chosen
Royston is a historic market town in Hertfordshire, England, known for the mysterious medieval Royston Cave and its position at the crossroads of ancient routes.
-
B.
Royston
Royston is a small coastal community in British Columbia, Canada, located just south of Courtenay in the Comox Valley on Vancouver Island.
-
C.
Royston
Royston is a masculine given name of English origin, used both as a first name and a surname.
-
D.
Royston
Royston is a residential district in the north of Glasgow, Scotland, known historically for its strong working-class and Irish Catholic community.
-
E.
Ruskington
Ruskington is a large village and civil parish in Lincolnshire, England, known for its rural character and position near the River Slea.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535e450c8190a2628245ae0d0bd3 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:48 p.m.