Triple
T22978367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldey Lighthouse |
E571387
|
entity |
| Predicate | warningRole |
P86402
|
FINISHED |
| Object | warns shipping of Caldey Island and nearby hazards |
—
|
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: warns shipping of Caldey Island and nearby hazards | Statement: [Caldey Lighthouse, warningRole, warns shipping of Caldey Island and nearby hazards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningRole Context triple: [Caldey Lighthouse, warningRole, warns shipping of Caldey Island and nearby hazards]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
warningSubject
Indicates that one entity is the topic or focus of a warning issued by another entity.
-
C.
warningOutcome
Indicates that a warning event leads to, results in, or is associated with a particular outcome or consequence.
-
D.
warningGivenBy
chosen
Indicates that one entity issues or delivers a warning to another entity.
-
E.
warningContent
Indicates that one entity provides the specific message, text, or material that constitutes a warning directed toward another entity or audience.
- 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_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. |
Created at: April 17, 2026, 3:49 p.m.