Triple
T36804787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic county of Worcestershire |
E909416
|
entity |
| Predicate | traditionalCountyOf |
P200731
|
FINISHED |
| Object | England |
—
|
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: England | Statement: [historic county of Worcestershire, traditionalCountyOf, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCountyOf Context triple: [historic county of Worcestershire, traditionalCountyOf, England]
-
A.
traditionalCountyIncludes
Indicates that a traditional or historic county geographically contains or encompasses another area or entity within its boundaries.
-
B.
ancestralCounty
Indicates that one entity is the county from which another entity or its ancestors originate.
-
C.
governingCountyTown
Indicates that a county has governmental authority over, and is administratively responsible for, a particular town.
-
D.
sharesCeremonialCountyWith
Indicates that two entities are located within the same ceremonial county.
-
E.
ceremonialCounty
Indicates that one entity is the ceremonial (non-administrative, often traditional or representational) county associated with the other 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
| PDg | Predicate description generation | batch_69ffa96638108190942dcfbe0516c37a |
completed | May 9, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:12 p.m.