Triple
T6400378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivatan people |
E144046
|
entity |
| Predicate | kanayi |
P70422
|
FINISHED |
| Object | rain cape made from voyavoy fiber |
—
|
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: rain cape made from voyavoy fiber | Statement: [Ivatan people, kanayi, rain cape made from voyavoy fiber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kanayi Context triple: [Ivatan people, kanayi, rain cape made from voyavoy fiber]
-
A.
kunya
Indicates the honorific or respectful name by which a person is addressed or referred to, typically reflecting esteem, modesty, or social standing.
-
B.
kāṇḍa
Indicates a part–whole relationship where something is a section, chapter, or subdivision of a larger structured whole.
-
C.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
D.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
E.
inker
Indicates that one entity serves as the inker for another, typically applying ink to finalize or enhance an existing drawing or artwork.
- F. None of above. chosen
Provenance (4 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c068994354819086cd51b661137f5a |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:35 p.m.