Triple
T5249784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckingham |
E118556
|
entity |
| Predicate | parliamentaryBoroughStatus |
P61735
|
FINISHED |
| Object | historic |
—
|
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: historic | Statement: [Buckingham, parliamentaryBoroughStatus, historic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentaryBoroughStatus Context triple: [Buckingham, parliamentaryBoroughStatus, historic]
-
A.
parliamentaryBoroughType
Indicates the specific classification or category of a parliamentary borough within a parliamentary or electoral system.
-
B.
isBoroughConstituency
Indicates that a parliamentary or electoral constituency is classified specifically as a borough constituency, as opposed to other constituency types.
-
C.
hasBoroughCouncil
Indicates that an administrative area is governed or overseen by a specific borough council.
-
D.
wasBoroughOrCountyConstituency
Indicates that something previously functioned as a parliamentary constituency defined at the borough or county level.
-
E.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b787b34819081af96de9355bb4f |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd787975788190848ffbac87896efe |
completed | March 20, 2026, 4:40 p.m. |
Created at: March 20, 2026, 1:50 p.m.