Triple
T32179890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kazy |
E821950
|
entity |
| Predicate | traditionalPreservation |
P21580
|
FINISHED |
| Object | drying |
—
|
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: drying | Statement: [kazy, traditionalPreservation, drying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPreservation Context triple: [kazy, traditionalPreservation, drying]
-
A.
preservationFocus
Indicates that the primary concern or emphasis is on maintaining, protecting, or conserving something in its existing or intended state.
-
B.
preservationMethod
chosen
Indicates the technique or process used to maintain, protect, or prolong the condition, quality, or usability of something over time.
-
C.
preservationUse
Indicates that something is used, designed, or intended specifically for the purpose of preserving or maintaining another entity in its existing state.
-
D.
preservationEra
Indicates the historical or temporal period during which something is preserved, conserved, or maintained.
-
E.
preservationType
Indicates the method or process by which something is preserved or kept from deterioration.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 12:34 a.m.