Triple
T27386247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgwater Town Bridge |
E691382
|
entity |
| Predicate | hasListingReason |
P156382
|
FINISHED |
| Object | architectural interest |
—
|
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: architectural interest | Statement: [Bridgwater Town Bridge, hasListingReason, architectural interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingReason Context triple: [Bridgwater Town Bridge, hasListingReason, architectural interest]
-
A.
listingReason
chosen
Indicates the reason or justification for why an item, entity, or subject has been listed or included in a particular collection, catalog, or context.
-
B.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
C.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
D.
hasListingSystem
Indicates that an entity is associated with or uses a particular system or mechanism for listing or cataloging items, entries, or information.
-
E.
reasonForDelisting
Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 12:24 p.m.