Triple
T18958205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Rock reef |
E463836
|
entity |
| Predicate | hasDangerousFeature |
P182
|
FINISHED |
| Object | dangerous shallows |
—
|
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: dangerous shallows | Statement: [Bell Rock reef, hasDangerousFeature, dangerous shallows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDangerousFeature Context triple: [Bell Rock reef, hasDangerousFeature, dangerous shallows]
-
A.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
E.
hasDiscoveryFeature
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d057a48190b82b5788b3281e28 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon