Triple
T20046037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Bann (County Wexford) |
E497559
|
entity |
| Predicate | landscapeTypeAlongCourse |
P71042
|
FINISHED |
| Object | rural landscape |
—
|
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: rural landscape | Statement: [River Bann (County Wexford), landscapeTypeAlongCourse, rural landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscapeTypeAlongCourse Context triple: [River Bann (County Wexford), landscapeTypeAlongCourse, rural landscape]
-
A.
landscapeType
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
-
B.
landscapeStyle
Indicates the design style or aesthetic approach applied to a landscape or outdoor environment.
-
C.
landscapeElement
Indicates that one entity functions as a landscape-related feature or component in relation to another entity.
-
D.
flowsThroughLandscape
chosen
Indicates that something (typically a fluid or moving entity) passes through or traverses a particular landscape or terrain.
-
E.
landscapeRole
Indicates the functional or symbolic role that an entity plays within a particular landscape or environmental setting.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632a5e888190ade41657ffd057f6 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.