Triple
T5216708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloucester (UK Parliament constituency) |
E117768
|
entity |
| Predicate | countyLabel |
P12149
|
FINISHED |
| Object | County |
—
|
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: County | Statement: [Gloucester (UK Parliament constituency), countyLabel, County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyLabel Context triple: [Gloucester (UK Parliament constituency), countyLabel, County]
-
A.
countyType
Indicates the classification or category of a county within an administrative or governmental system.
-
B.
countyName
chosen
Indicates the specific name assigned to a county in which an entity is located or with which it is associated.
-
C.
countyRegion
Indicates that a county is located within, or is administratively part of, a larger geographic region.
-
D.
countyEquivalent
Indicates that two territorial or administrative units are considered equivalent in status or function to a county within a given governmental or geographic framework.
-
E.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a95abdc8190b0babd79cea1360e |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.