Triple
T13685131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Needles Lighthouse |
E328101
|
entity |
| Predicate | protectsShippingFrom |
P1040
|
FINISHED |
| Object | treacherous waters around The Needles |
—
|
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: treacherous waters around The Needles | Statement: [The Needles Lighthouse, protectsShippingFrom, treacherous waters around The Needles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsShippingFrom Context triple: [The Needles Lighthouse, protectsShippingFrom, treacherous waters around The Needles]
-
A.
protectsShippingTo
Indicates that one entity safeguards or ensures the security of shipping or delivery directed toward another entity.
-
B.
protects
chosen
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
C.
shippingAccess
Indicates that one entity has the ability or permission to ship items to or on behalf of another entity.
-
D.
primaryCargoProtected
Indicates that the main cargo associated with an entity is safeguarded or shielded from harm, loss, or interference.
-
E.
shippingRisk
Indicates the level or likelihood of potential loss, damage, or delay associated with transporting goods from one location to another.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66f8acc8190b2a82b722930b995 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.