Triple
T20846093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surrey |
E513228
|
entity |
| Predicate | historicCountyStatusFrom |
P19842
|
FINISHED |
| Object | Anglo-Saxon period |
—
|
LITERAL 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: Anglo-Saxon period | Statement: [Surrey, historicCountyStatusFrom, Anglo-Saxon period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCountyStatusFrom Context triple: [Surrey, historicCountyStatusFrom, Anglo-Saxon period]
-
A.
hasHistoricCountyStatusSince
chosen
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
B.
historicCountyStatusRetained
Indicates that an entity has maintained or preserved its official status as a historic county without interruption or loss.
-
C.
historicCountyPart
Indicates that one entity forms a constituent part or subdivision of a historic county.
-
D.
hasHistoricRegistrationCountyStatus
Indicates that an entity holds or has held official historic registration status within a particular county.
-
E.
hasHistoricCountyCode
Indicates that an entity is associated with a specific historic county, identified by its county code.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34ec254819082610264c7af20c8 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.