Triple
T25427941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiljainen kansa |
E637166
|
entity |
| Predicate | hasClothingFeature |
P110046
|
FINISHED |
| Object | clothes changed periodically |
—
|
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: clothes changed periodically | Statement: [Hiljainen kansa, hasClothingFeature, clothes changed periodically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClothingFeature Context triple: [Hiljainen kansa, hasClothingFeature, clothes changed periodically]
-
A.
clothingFeature
chosen
Indicates that one entity has a specific clothing-related attribute, detail, or characteristic associated with it.
-
B.
hasGarment
Indicates that one entity possesses, wears, or is associated with a particular garment.
-
C.
wardrobeFeature
Indicates that a wardrobe possesses or includes a specific feature, attribute, or functional element.
-
D.
hasClothingSource
Indicates that an entity’s clothing originates from, is supplied by, or is obtained through a specified source.
-
E.
coatCharacteristic
Indicates that one entity has a particular property, feature, or quality that characterizes its outer covering or surface.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:57 p.m.