Triple
T9486985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lorica segmentata |
E228785
|
entity |
| Predicate | archaeologicalSites |
P1098
|
FINISHED |
| Object | Corbridge |
E529640
|
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: Corbridge | Statement: [lorica segmentata, archaeologicalSites, Corbridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Corbridge Context triple: [lorica segmentata, archaeologicalSites, Corbridge]
-
A.
Corbridge
chosen
Corbridge is a historic village in Northumberland, England, known for its Roman heritage and picturesque setting on the banks of the River Tyne.
-
B.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
C.
Buntingford
Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
-
D.
Curbridge
Curbridge is a small rural village in Oxfordshire, England, situated within the district of West Oxfordshire.
-
E.
Gadebridge
Gadebridge is a residential area and suburb of Hemel Hempstead in Hertfordshire, England.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd8051303881909566126a2688e41c |
completed | April 1, 2026, 8:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12d1326b8819084c6d9490b7a96dc |
completed | April 4, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:55 p.m.