Triple
T22978366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldey Lighthouse |
E571387
|
entity |
| Predicate | visibilitySector |
P150477
|
FINISHED |
| Object | seaward arc off Caldey Island |
—
|
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: seaward arc off Caldey Island | Statement: [Caldey Lighthouse, visibilitySector, seaward arc off Caldey Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilitySector Context triple: [Caldey Lighthouse, visibilitySector, seaward arc off Caldey Island]
-
A.
coveredSector
Indicates that one entity provides coverage, service, or operational responsibility for a particular sector or area.
-
B.
observedBySector
Indicates that something (such as an event, object, or phenomenon) is monitored, detected, or recorded by a specific sector or segment.
-
C.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
D.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
E.
visibilityComputation
Indicates the process or relationship by which the visibility of one entity from another is determined or computed.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18293f830819095cca91af7abd742 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:49 p.m.