Triple
T9893999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikimoto cultured pearls |
E181522
|
entity |
| Predicate | hasCraftsmanshipStandard |
P77076
|
FINISHED |
| Object | hand-selected matching |
—
|
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: hand-selected matching | Statement: [Mikimoto cultured pearls, hasCraftsmanshipStandard, hand-selected matching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCraftsmanshipStandard Context triple: [Mikimoto cultured pearls, hasCraftsmanshipStandard, hand-selected matching]
-
A.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
B.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
C.
hasCraftsmanGod
Indicates that an entity has an associated deity specifically responsible for craftsmanship or artisan skills.
-
D.
isHandmade
chosen
Indicates that an object has been crafted or produced by hand rather than by automated or industrial processes.
-
E.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb48271d48190b718c7f6b2fe315b |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.