Triple
T18958217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Rock reef |
E463836
|
entity |
| Predicate | shippingHazardSince |
P133956
|
FINISHED |
| Object | ancient times |
—
|
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: ancient times | Statement: [Bell Rock reef, shippingHazardSince, ancient times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingHazardSince Context triple: [Bell Rock reef, shippingHazardSince, ancient times]
-
A.
shippingRisk
Indicates the level or likelihood of potential loss, damage, or delay associated with transporting goods from one location to another.
-
B.
hasHazardousMaterialsRestrictions
Indicates that there are rules or limitations governing the presence, handling, or transport of hazardous materials in relation to the subject.
-
C.
hazmatSupport
Indicates that one entity provides hazardous materials (hazmat) response or support services to another entity or situation.
-
D.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
E.
hasHealthWarningOnPackaging
Indicates that an item’s packaging displays a health-related warning message or symbol.
- 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_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. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon