Triple
T29073210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Custos Rotulorum of King’s County |
E735862
|
entity |
| Predicate | modernCountyName |
P12149
|
FINISHED |
| Object | County Offaly |
—
|
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: County Offaly | Statement: [Custos Rotulorum of King’s County, modernCountyName, County Offaly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCountyName Context triple: [Custos Rotulorum of King’s County, modernCountyName, County Offaly]
-
A.
countyName
chosen
Indicates the specific name assigned to a county in which an entity is located or with which it is associated.
-
B.
isNamedCountyOf
Indicates that a county bears a specific official name within a given jurisdiction or context.
-
C.
majorCounty
Indicates that a county holds primary or significant administrative, economic, or demographic importance within a larger region or jurisdiction.
-
D.
historicalCounty
Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
-
E.
cityCounty
Indicates that a city is located within, and administratively belongs to, a specific county.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 10:21 a.m.