Triple
T4108686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikwerre people |
E88515
|
entity |
| Predicate | nativeDress |
P19523
|
FINISHED |
| Object | wrapper and shirt with traditional cap for men |
—
|
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: wrapper and shirt with traditional cap for men | Statement: [Ikwerre people, nativeDress, wrapper and shirt with traditional cap for men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeDress Context triple: [Ikwerre people, nativeDress, wrapper and shirt with traditional cap for men]
-
A.
nationalDress
chosen
Indicates that an item of clothing is recognized as the traditional or customary dress associated with a particular nation or culture.
-
B.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
C.
dressFeature
Indicates that a dress possesses or is characterized by a particular feature, attribute, or design element.
-
D.
notableOutfit
Indicates that an entity is known for or associated with wearing a particular outfit or style of clothing.
-
E.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:40 p.m.