Triple
T29349191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romford (UK Parliament constituency) |
E744254
|
entity |
| Predicate | containsWards |
P14475
|
FINISHED |
| Object | Romford Town (ward) |
—
|
NE NERFINISHED |
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: Romford Town (ward) | Statement: [Romford (UK Parliament constituency), containsWards, Romford Town (ward)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWards Context triple: [Romford (UK Parliament constituency), containsWards, Romford Town (ward)]
-
A.
containsWard
chosen
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.
-
B.
numberOfWards
Indicates the quantitative relationship specifying how many wards are associated with a given entity.
-
C.
isWardOf
Indicates that one entity is under the guardianship, protection, or legal care of another entity as their ward.
-
D.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
-
E.
hasMunicipalWards
Indicates that a municipality is divided into and associated with one or more municipal wards as its internal administrative units.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 28, 2026, 2:05 p.m.