Triple
T26787617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savu Island |
E670427
|
entity |
| Predicate | hasTraditionalTextileMotive |
P51314
|
FINISHED |
| Object | geometric patterns |
—
|
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: geometric patterns | Statement: [Savu Island, hasTraditionalTextileMotive, geometric patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalTextileMotive Context triple: [Savu Island, hasTraditionalTextileMotive, geometric patterns]
-
A.
hasFlowerMotif
Indicates that one entity features or is decorated with a flower-themed design or pattern in relation to another entity.
-
B.
hasPatrioticMotif
Indicates that something incorporates a theme, symbol, or element expressing patriotism or national pride.
-
C.
textileFeature
Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
-
D.
traditionalMotif
chosen
Indicates that something incorporates, represents, or is characterized by a motif rooted in established cultural or historical traditions.
-
E.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 27, 2026, 4:13 a.m.