Triple
T26259545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caradon Mining District |
E656808
|
entity |
| Predicate | landscapeCharacterizedBy |
P45658
|
FINISHED |
| Object | engine house ruins |
—
|
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: engine house ruins | Statement: [Caradon Mining District, landscapeCharacterizedBy, engine house ruins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscapeCharacterizedBy Context triple: [Caradon Mining District, landscapeCharacterizedBy, engine house ruins]
-
A.
landscapeType
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
-
B.
landscapeRole
Indicates the functional or symbolic role that an entity plays within a particular landscape or environmental setting.
-
C.
landscapeElement
chosen
Indicates that one entity functions as a landscape-related feature or component in relation to another entity.
-
D.
landscapeStyle
Indicates the design style or aesthetic approach applied to a landscape or outdoor environment.
-
E.
landscapeValue
Indicates the assessed aesthetic, cultural, or ecological worth attributed to a particular landscape or scenery.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfdd57c81908d069fc4b8124ff7 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:09 p.m.