Triple
T832290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Native Hawaiians |
E17991
|
entity |
| Predicate | traditionalGarment |
P19523
|
FINISHED |
| Object | malo |
—
|
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: malo | Statement: [Native Hawaiians, traditionalGarment, malo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalGarment Context triple: [Native Hawaiians, traditionalGarment, malo]
-
A.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
B.
nationalDress
chosen
Indicates that an item of clothing is recognized as the traditional or customary dress associated with a particular nation or culture.
-
C.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
D.
traditionalGift
Indicates that one entity customarily gives another entity a gift in accordance with established traditions or cultural practices.
-
E.
traditionalStatus
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb647988190950e1790bcfa60a5 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.