Triple
T37405852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradford city centre parish |
E929127
|
entity |
| Predicate | hasCentralAreaFocus |
P133049
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bradford city centre parish, hasCentralAreaFocus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralAreaFocus Context triple: [Bradford city centre parish, hasCentralAreaFocus, true]
-
A.
hasPrimaryFocusRegion
chosen
Indicates that something is chiefly concerned with, centered on, or directed toward a particular geographic or spatial region.
-
B.
hasZoningFocus
Indicates that an entity is primarily concerned with or directed toward a particular zoning category, regulation, or land-use designation.
-
C.
hasProgramFocus
Indicates that an entity (such as a program or initiative) is oriented around or primarily concerned with a particular thematic area, topic, or objective.
-
D.
hasPrimaryFocus
Indicates that something is the main subject, concern, or area of attention for an entity or activity.
-
E.
hasPrimaryInstrumentFocus
Indicates that an entity’s main emphasis or specialization is centered on a particular instrument.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:16 p.m.