Triple
T18456017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Başpehlivan |
E450904
|
entity |
| Predicate | wornAttire |
P271
|
FINISHED |
| Object | kispet (leather trousers) |
—
|
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: kispet (leather trousers) | Statement: [Başpehlivan, wornAttire, kispet (leather trousers)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wornAttire Context triple: [Başpehlivan, wornAttire, kispet (leather trousers)]
-
A.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
B.
usualAttire
Indicates the type of clothing an entity typically wears in ordinary or characteristic situations.
-
C.
wears
chosen
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
D.
oftenDepictedWearing
Indicates that an entity is frequently shown or represented as wearing a particular item or type of clothing in depictions or portrayals.
-
E.
typicallyWornBy
Indicates that something (such as an item or garment) is most commonly or characteristically worn by a particular type of person or group.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264c10408190b2085ade88655c7d |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.