Triple
T19006940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skerryvore Lighthouse (improvements and maintenance) |
E465112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lighthouse maintenance program |
C41509
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: lighthouse maintenance program Context triple: [Skerryvore Lighthouse (improvements and maintenance), instanceOf, lighthouse maintenance program]
-
A.
lighthouse engineer
A lighthouse engineer is a specialist who designs, maintains, and optimizes lighthouse structures and their navigational systems to ensure safe maritime passage.
-
B.
coastal lighthouse
A coastal lighthouse is a tall, often cylindrical structure built along shorelines to emit a guiding light and navigational signals that warn ships of hazards and help them safely navigate coastal waters.
-
C.
lighthouse complex
A lighthouse complex is a coastal facility comprising the lighthouse tower and its associated buildings, equipment, and infrastructure that together support the operation, maintenance, and habitation required for safe maritime navigation.
-
D.
cast-iron lighthouse
A cast-iron lighthouse is a navigational tower constructed primarily from prefabricated cast-iron plates or segments, designed to withstand harsh marine environments while housing a light to guide vessels safely.
-
E.
ornamental lighthouse
An ornamental lighthouse is a decorative structure or object, often miniature or stylized, designed to aesthetically evoke the form and symbolism of a real lighthouse without serving a functional navigational purpose.
- F. None of above. chosen
Provenance (1 batch)
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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:01 p.m.