Triple
T7221606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Deals |
E150271
|
entity |
| Predicate | typicalProject |
P37446
|
FINISHED |
| Object | town centre regeneration |
—
|
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: town centre regeneration | Statement: [Town Deals, typicalProject, town centre regeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProject Context triple: [Town Deals, typicalProject, town centre regeneration]
-
A.
typicalProjectTypes
chosen
Indicates the kinds or categories of projects that are most commonly or characteristically associated with a given entity.
-
B.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
-
C.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
D.
subjectOfProject
Indicates that an entity serves as the main focus, topic, or target of a particular project.
-
E.
parentProject
Indicates that one project serves as the direct higher-level or containing project in relation to another project.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b42c5c81908c405f161c35ffb4 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:54 p.m.