Triple
T16022598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Island Light |
E388638
|
entity |
| Predicate | nearbyHazard |
P63246
|
FINISHED |
| Object | shoals and strong currents |
—
|
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: shoals and strong currents | Statement: [Pilot Island Light, nearbyHazard, shoals and strong currents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyHazard Context triple: [Pilot Island Light, nearbyHazard, shoals and strong currents]
-
A.
hasObjectiveHazards
chosen
Indicates that an entity is associated with concrete, externally verifiable dangers or risks.
-
B.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
C.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
D.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
-
E.
nearbyWildfire
Indicates that a wildfire is occurring close enough to a given location or entity to be considered in its immediate vicinity.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.