Triple
T14995634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab-Norman architecture |
E373951
|
entity |
| Predicate | employedCraftsmenFrom |
P116272
|
FINISHED |
| Object | Islamic world |
—
|
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: Islamic world | Statement: [Arab-Norman architecture, employedCraftsmenFrom, Islamic world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedCraftsmenFrom Context triple: [Arab-Norman architecture, employedCraftsmenFrom, Islamic world]
-
A.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
B.
traditionalCraft
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
C.
craftGuild
Indicates that an entity is a member of, affiliated with, or governed by a particular craft guild organization.
-
D.
craftSpecialty
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
E.
hasCraftsmanGod
Indicates that an entity has an associated deity specifically responsible for craftsmanship or artisan skills.
- F. None of above. chosen
Provenance (4 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded718e4288190b5e144f82299a194 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:53 a.m.