Triple
T20513080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Blas neighborhood (Cusco) |
E503611
|
entity |
| Predicate | typicalCraft |
P5963
|
FINISHED |
| Object | textiles |
—
|
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: textiles | Statement: [San Blas neighborhood (Cusco), typicalCraft, textiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCraft Context triple: [San Blas neighborhood (Cusco), typicalCraft, textiles]
-
A.
traditionalCraft
chosen
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
B.
craftSpecialty
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
C.
associatedCraftsmen
Indicates that there is a relationship linking an entity to one or more craftsmen who are connected to it through work, creation, or service.
-
D.
craftedIn
Indicates that an object or work was created or produced at a particular place or within a specific location.
-
E.
hasNotableCraft
Indicates that an entity is associated with a particularly significant or distinguished craft, skill, or artisanal practice.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcd74c48190b050e25c20154c09 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.