Triple
T5116766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penryn |
E115353
|
entity |
| Predicate | formerBoroughAbolished |
P24088
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Penryn, formerBoroughAbolished, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerBoroughAbolished Context triple: [Penryn, formerBoroughAbolished, 19th century]
-
A.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
B.
historicCountyAbolishedAsAdministrativeUnit
Indicates that a historic county ceased to function as an official administrative unit.
-
C.
boroughOf
chosen
Indicates that one place is a borough that is administratively or geographically part of another, typically larger, municipal entity.
-
D.
existedAsCountyOfDistrictOfColumbiaUntil
Indicates that an entity functioned as a county within the District of Columbia up to a specified end date or time.
-
E.
wasBoroughOrCountyConstituency
Indicates that something previously functioned as a parliamentary constituency defined at the borough or county level.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cfa9f88190aa7dfd264e554899 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd7160d44081908cc64f3c14d28b81 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.