Triple
T28625550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings—Hants |
E724510
|
entity |
| Predicate | hasPredecessorRiding |
P198785
|
FINISHED |
| Object | Colchester—Hants |
—
|
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: Colchester—Hants | Statement: [Kings—Hants, hasPredecessorRiding, Colchester—Hants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredecessorRiding Context triple: [Kings—Hants, hasPredecessorRiding, Colchester—Hants]
-
A.
predecessorRiding
Indicates that one entity is riding or mounted on another entity that is its predecessor in some defined sequence or ordering.
-
B.
hasRidingAssociation
Indicates an association where one entity is related to another through the act or context of riding (e.g., serving as rider, mount, or riding partner).
-
C.
hasPredecessorSeat
Indicates that one seat directly precedes another seat in an ordered sequence or arrangement.
-
D.
hasOwnerRider
Indicates that an entity (such as an animal or vehicle) has a specific person who both owns it and rides or uses it.
-
E.
isRiddenBy
Indicates that an entity serves as a mount or vehicle that is being ridden by another entity.
- F. None of above. chosen
Provenance (4 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69ff069ddf948190bdfe438953249dd0 |
completed | May 9, 2026, 10:04 a.m. |
Created at: April 28, 2026, 4:35 a.m.