Triple
T16351654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batsbi |
E397073
|
entity |
| Predicate | traditionalDressSimilarTo |
P123079
|
FINISHED |
| Object | Georgian highlanders |
—
|
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: Georgian highlanders | Statement: [Batsbi, traditionalDressSimilarTo, Georgian highlanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDressSimilarTo Context triple: [Batsbi, traditionalDressSimilarTo, Georgian highlanders]
-
A.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
-
B.
traditionalDressColor
Indicates the color associated with an entity’s traditional or customary dress or clothing.
-
C.
nationalDress
Indicates that an item of clothing is recognized as the traditional or customary dress associated with a particular nation or culture.
-
D.
hasTraditionalAttire
Indicates that an entity possesses or is associated with clothing that is customary or traditional within a particular culture or community.
-
E.
garmentType
Indicates the specific kind or category of garment associated with an entity.
- F. None of above. chosen
Provenance (4 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facbf60c8190aa47d4c45ff59354 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.