Triple
T6400377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivatan people |
E144046
|
entity |
| Predicate | vakul |
P70421
|
FINISHED |
| Object | headgear 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: headgear made from voyavoy fiber | Statement: [Ivatan people, vakul, headgear made from voyavoy fiber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vakul Context triple: [Ivatan people, vakul, headgear made from voyavoy fiber]
-
A.
via
Indicates that something occurs, is achieved, or is connected by means of, through the use of, or along the route of another entity or medium.
-
B.
rukus
Indicates that an entity is associated with or participates in a disturbance, commotion, or noisy disruptive event involving another entity.
-
C.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
D.
victor
Indicates that one entity is the winner or has prevailed over another in a contest, conflict, or competition.
-
E.
wand
Indicates that one entity uses or possesses a wand as an instrument or tool in relation to another entity or action.
- 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.