Triple
T582290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nenets |
E15083
|
entity |
| Predicate | traditionalClothingMaterial |
P1272
|
FINISHED |
| Object | reindeer hide |
—
|
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: reindeer hide | Statement: [Nenets, traditionalClothingMaterial, reindeer hide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalClothingMaterial Context triple: [Nenets, traditionalClothingMaterial, reindeer hide]
-
A.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
B.
tartan
Indicates that something has a tartan pattern or is characterized by a tartan design.
-
C.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
traditionalLifestyle
Indicates that an entity follows or maintains long-established customs, practices, and ways of living, typically in contrast to modern or industrialized lifestyles.
-
E.
traditionalCraft
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.