Triple
T35595711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Battalion, Royal Anglian Regiment |
E1028624
|
entity |
| Predicate | traditionalRecruitingCounty |
P3505
|
FINISHED |
| Object | Essex |
—
|
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: Essex | Statement: [3rd Battalion, Royal Anglian Regiment, traditionalRecruitingCounty, Essex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRecruitingCounty Context triple: [3rd Battalion, Royal Anglian Regiment, traditionalRecruitingCounty, Essex]
-
A.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
B.
traditionalSeatCounty
Indicates that a location serves as the historically recognized administrative or ceremonial county seat for a given county.
-
C.
homeCounty
chosen
Indicates that a specified county is the primary home or place of residence for a given person or entity.
-
D.
traditionalCountyIncludes
Indicates that a traditional or historic county geographically contains or encompasses another area or entity within its boundaries.
-
E.
startCounty
Indicates the county in which something (such as an event, route, or process) begins or originates.
- F. None of above.
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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.