Triple
T10426632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weymouth, Dorset, England |
E245804
|
entity |
| Predicate | hasSeafrontStyle |
P93523
|
FINISHED |
| Object | Georgian terraces |
—
|
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: Georgian terraces | Statement: [Weymouth, Dorset, England, hasSeafrontStyle, Georgian terraces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeafrontStyle Context triple: [Weymouth, Dorset, England, hasSeafrontStyle, Georgian terraces]
-
A.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
B.
hasWaterfrontView
Indicates that a property or location offers a direct view of a body of water from its premises.
-
C.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
D.
hasWaterfrontArea
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
E.
coastalFrontageFor
Indicates that one entity has a boundary or frontage directly along the coast associated with another entity.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea498ab08190b451c0b257c0711b |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:12 p.m.