Triple
T27617107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakan |
E700466
|
entity |
| Predicate | traditionalDesignFeature |
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: [Yakan, traditionalDesignFeature, geometric patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDesignFeature Context triple: [Yakan, traditionalDesignFeature, geometric patterns]
-
A.
traditionalMotif
chosen
Indicates that something incorporates, represents, or is characterized by a motif rooted in established cultural or historical traditions.
-
B.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
-
C.
typicalDesignElement
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
D.
usesDesignTradition
Indicates that one entity creates, interprets, or operates according to the established design principles, styles, or conventions associated with another entity or tradition.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 2:13 p.m.