Triple
T5278566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leeds City Council |
E119433
|
entity |
| Predicate | numberOfWards |
P63824
|
FINISHED |
| Object | 33 |
—
|
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: 33 | Statement: [Leeds City Council, numberOfWards, 33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfWards Context triple: [Leeds City Council, numberOfWards, 33]
-
A.
numberOfSpecialWards
Indicates the count of wards that are designated as special within a given context or entity.
-
B.
containsWard
Indicates that one entity includes, encompasses, or has within it a ward (such as a district, division, or dependent person) as part of its scope or responsibility.
-
C.
numberOfDistricts
Indicates the total count of districts associated with a given entity or area.
-
D.
hasNumberOfCouncillors
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
E.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd8c9b82ac819080e798713c0bb4d8 |
completed | March 20, 2026, 6:06 p.m. |
Created at: March 20, 2026, 1:51 p.m.