Triple
T15457487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Glamorgan County Council |
E371807
|
entity |
| Predicate | hasGovernmentOfficeType |
P5164
|
FINISHED |
| Object | county hall |
—
|
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 hall | Statement: [South Glamorgan County Council, hasGovernmentOfficeType, county hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentOfficeType Context triple: [South Glamorgan County Council, hasGovernmentOfficeType, county hall]
-
A.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
B.
hasOfficeType
chosen
Indicates that an entity’s office is classified as a specific type or category of office.
-
C.
governsOfficeType
Indicates that an entity has authoritative control or regulatory oversight over a particular type or category of office.
-
D.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
E.
targetGovernmentType
Indicates the form or system of governance that an entity is directed toward, associated with, or intended to influence.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1623f0819086f6fc2bfd536609 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:31 a.m.