Triple
T38306288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigg and Cleethorpes |
E1032352
|
entity |
| Predicate | administrativeCountyLater |
P65227
|
FINISHED |
| Object | North Lincolnshire |
—
|
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 Lincolnshire | Statement: [Brigg and Cleethorpes, administrativeCountyLater, North Lincolnshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeCountyLater Context triple: [Brigg and Cleethorpes, administrativeCountyLater, North Lincolnshire]
-
A.
laterAdministrativeRegion
chosen
Indicates that an entity became part of, or was replaced by, another administrative region at a later point in time.
-
B.
subsequentCounty
Indicates that one county follows another in a defined sequence, such as chronological order of creation or administrative succession.
-
C.
hasPostalAddressCounty
Indicates that an entity’s postal address is located within a specified county.
-
D.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
E.
hasCountyAdministration
Indicates that an entity is governed, managed, or served by a specific county-level administrative authority.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:30 p.m.