Triple
T9586976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bath Weir |
E231314
|
entity |
| Predicate | partOfView |
P48736
|
FINISHED |
| Object | iconic postcard views of Bath |
—
|
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: iconic postcard views of Bath | Statement: [Bath Weir, partOfView, iconic postcard views of Bath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfView Context triple: [Bath Weir, partOfView, iconic postcard views of Bath]
-
A.
partOfScene
chosen
Indicates that one entity functions as a component or element within a larger scene or setting involving another entity.
-
B.
partOfSingle
Indicates that one entity is a component or member of exactly one specific whole or collection, and not shared among multiple such wholes.
-
C.
partOfType
Indicates that one entity represents a component, segment, or subset that belongs to or is included within the type or category represented by another entity.
-
D.
structurePartOf
Indicates that one structure is a constituent or component of a larger, encompassing structure.
-
E.
partOfFront
Indicates that one entity constitutes a component or section located at the front portion of another entity.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99eed8288190b74de991bb55b15b |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.