Triple
T14058171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adanwomase |
E338271
|
entity |
| Predicate | hasWeavingTechnique |
P3047
|
FINISHED |
| Object | strip weaving |
—
|
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: strip weaving | Statement: [Adanwomase, hasWeavingTechnique, strip weaving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeavingTechnique Context triple: [Adanwomase, hasWeavingTechnique, strip weaving]
-
A.
hasWeave
Indicates that one entity possesses, exhibits, or is characterized by a particular weave or woven pattern associated with another entity.
-
B.
weavingCenter
Indicates that an entity serves as a central place or hub where weaving activities are carried out or coordinated.
-
C.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
D.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
E.
weavingCommunity
Indicates a relationship where individuals participate together in the shared practice, culture, or organization of weaving as a community activity.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.