Triple
T11670713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotunda (Stowe) |
E277368
|
entity |
| Predicate | landscapeFunction |
P43944
|
FINISHED |
| Object | eye-catcher |
—
|
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: eye-catcher | Statement: [Rotunda (Stowe), landscapeFunction, eye-catcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscapeFunction Context triple: [Rotunda (Stowe), landscapeFunction, eye-catcher]
-
A.
landscapeRole
chosen
Indicates the functional or symbolic role that an entity plays within a particular landscape or environmental setting.
-
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.
landscapeConcept
Indicates a conceptual or thematic relationship involving landscapes, such as ideas, interpretations, or abstract representations of landscape.
-
E.
landscapeType
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a44264c08190ba1a4a5bcdc9367b |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.