Triple
T10383853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirakawa-go region |
E244708
|
entity |
| Predicate | roofDesignPurpose |
P13382
|
FINISHED |
| Object | to shed heavy snowfall |
—
|
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: to shed heavy snowfall | Statement: [Shirakawa-go region, roofDesignPurpose, to shed heavy snowfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofDesignPurpose Context triple: [Shirakawa-go region, roofDesignPurpose, to shed heavy snowfall]
-
A.
roofOptions
Indicates the available types or configurations of roofs that can be selected or applied to an entity.
-
B.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
C.
purposeOfConstruction
Indicates that one entity was constructed or built in order to serve, enable, or fulfill the function, goal, or intended use represented by another entity.
-
D.
hasTypeOfRoof
Indicates that an entity possesses or is characterized by a specific kind or style of roof.
-
E.
roofFunction
chosen
Indicates the functional role or purpose that a roof serves in relation to the structure it covers.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a2aafc8190aa11d14852fa1599 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.