Triple
T11416885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Category A listed building |
E270513
|
entity |
| Predicate | impactOnOwner |
P99191
|
FINISHED |
| Object | restrictions on alterations |
—
|
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: restrictions on alterations | Statement: [Category A listed building, impactOnOwner, restrictions on alterations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnOwner Context triple: [Category A listed building, impactOnOwner, restrictions on alterations]
-
A.
impactOnMarket
Indicates the effect or influence that one factor, event, or action has on market conditions, behavior, or outcomes.
-
B.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
C.
impactOnBusiness
Indicates the effect or influence that one factor, event, or action has on a business’s performance, operations, or outcomes.
-
D.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
E.
impactIfCompleted
Indicates the effect or consequence that will occur if the referenced task or action is fully completed.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b0236c81908122ce3fc7b4fde7 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.