Triple
T24376680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rote |
E614493
|
entity |
| Predicate | hasTraditionalHeadgear |
P31655
|
FINISHED |
| Object | Ti’i langga hat |
—
|
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: Ti’i langga hat | Statement: [Rote, hasTraditionalHeadgear, Ti’i langga hat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalHeadgear Context triple: [Rote, hasTraditionalHeadgear, Ti’i langga hat]
-
A.
traditionalHeaddress
Indicates that an entity wears or is associated with a culturally traditional headdress as part of customary or ceremonial attire.
-
B.
hasTraditionalAttire
Indicates that an entity possesses or is associated with clothing that is customary or traditional within a particular culture or community.
-
C.
haveCeremonialHead
Indicates that one entity serves as the formal or symbolic head or leader of another entity, typically without holding full executive power.
-
D.
hasHeadbandType
Indicates that an entity is associated with a specific type or style of headband.
-
E.
associatedWithHeadgear
chosen
Indicates a relationship where an entity is connected or related to a particular item of headgear, such as by wearing, using, or being characterized by it.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d7fb188190bfab5e7ff83fa884 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.