Triple
T35533290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callala Beach |
E1026860
|
entity |
| Predicate | safetyCharacteristics |
P63490
|
FINISHED |
| Object | generally sheltered conditions |
—
|
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: generally sheltered conditions | Statement: [Callala Beach, safetyCharacteristics, generally sheltered conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyCharacteristics Context triple: [Callala Beach, safetyCharacteristics, generally sheltered conditions]
-
A.
hasSafetyCharacteristic
chosen
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
B.
safetyProfile
Indicates the overall level and characteristics of risk or harm associated with something, typically summarizing how safe it is under specified conditions.
-
C.
safetyRatingHighlight
Indicates that an entity’s safety rating is emphasized or specially marked as noteworthy compared to others.
-
D.
securityFeaturesInclude
Indicates that a system, product, or environment possesses or is equipped with specific security features as part of its protective measures.
-
E.
safetyCategory
Indicates the classification of something according to its level or type of safety.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.