Triple
T19267834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wakakusa-yama |
E481834
|
entity |
| Predicate | safetyMeasureForYamayaki |
P41950
|
FINISHED |
| Object | controlled burning |
—
|
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: controlled burning | Statement: [Wakakusa-yama, safetyMeasureForYamayaki, controlled burning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyMeasureForYamayaki Context triple: [Wakakusa-yama, safetyMeasureForYamayaki, controlled burning]
-
A.
avoidsBurningWhen
Indicates that one entity does not burn under certain specified conditions or circumstances.
-
B.
measuresSafetyUsing
chosen
Indicates that an entity evaluates or assesses safety by employing a specified method, tool, or standard.
-
C.
safetyRationale
Indicates the reasoning or justification provided to explain how and why something is considered safe or made safe.
-
D.
safetyAdvice
Indicates that one entity provides guidance or recommendations to another entity about how to avoid danger or reduce risk in a particular context.
-
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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8e1f888190a95f60fa29ca3b98 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.