Triple
T3105384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcastle City Council |
E64817
|
entity |
| Predicate | governingBodySeats |
P45958
|
FINISHED |
| Object | councillors |
—
|
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: councillors | Statement: [Newcastle City Council, governingBodySeats, councillors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodySeats Context triple: [Newcastle City Council, governingBodySeats, councillors]
-
A.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
B.
seatOfCouncil
Indicates that a location serves as the official meeting place or headquarters of a council.
-
C.
governingBody2
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
-
D.
hasMinisterialSeat
Indicates that a governmental or administrative body holds its official ministerial seat or headquarters at a particular location.
-
E.
legislativeCouncilSeats
Indicates the number of seats held or allocated in a legislative council within a given political or administrative context.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29a90e88190afb8a10291ef1946 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.