Triple
T28927629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North East Hertfordshire |
E733692
|
entity |
| Predicate | hasDistrictPart |
P192490
|
FINISHED |
| Object | North Hertfordshire District |
—
|
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: North Hertfordshire District | Statement: [North East Hertfordshire, hasDistrictPart, North Hertfordshire District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistrictPart Context triple: [North East Hertfordshire, hasDistrictPart, North Hertfordshire District]
-
A.
hasCityDistrictAlong
Indicates that a city district is located along or adjacent to a specified linear feature, such as a road, river, or coastline.
-
B.
hasDistrictKey
Indicates that an entity is associated with a specific district through a unique identifying key.
-
C.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
D.
hasCityDistrictCode
Indicates that a city district is associated with a specific identifying code.
-
E.
geographicallySeparatedDistrictOf
Indicates that one district is a non-contiguous, physically separate part of another district or administrative area.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: April 28, 2026, 8:25 a.m.