Triple
T14058128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonwire |
E338270
|
entity |
| Predicate | hasCraftSpecialization |
P98026
|
FINISHED |
| Object | loom 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: loom weaving | Statement: [Bonwire, hasCraftSpecialization, loom weaving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCraftSpecialization Context triple: [Bonwire, hasCraftSpecialization, loom weaving]
-
A.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
B.
craftSpecialty
chosen
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
C.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
D.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
E.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
- 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.