Triple
T19950608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish regiments |
E479543
|
entity |
| Predicate | wearsDressItem |
P271
|
FINISHED |
| Object | kilt |
—
|
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: kilt | Statement: [Scottish regiments, wearsDressItem, kilt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearsDressItem Context triple: [Scottish regiments, wearsDressItem, kilt]
-
A.
usesDressing
Indicates that one entity applies or employs a particular dressing (such as a sauce, covering, or treatment) in relation to another entity or context.
-
B.
wears
chosen
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
C.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
-
D.
dressFeature
Indicates that a dress possesses or is characterized by a particular feature, attribute, or design element.
-
E.
hasDressCircle
Indicates that something (typically a theater or venue) includes or is equipped with a dress circle seating area.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6b694c819080daea9422bcdd38 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.