Triple
T37245755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chordeleg |
E923845
|
entity |
| Predicate | hasTypeOfArtisanWork |
P133936
|
FINISHED |
| Object | metalworking |
—
|
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: metalworking | Statement: [Chordeleg, hasTypeOfArtisanWork, metalworking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfArtisanWork Context triple: [Chordeleg, hasTypeOfArtisanWork, metalworking]
-
A.
hasWorkshopType
Indicates that an entity is associated with, classified by, or offers a specific type or category of workshop.
-
B.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
C.
hasTypeOfWorkExhibited
chosen
Indicates that a subject (such as an exhibition or venue) features or displays a particular type or category of work.
-
D.
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.
-
E.
isOccupationalFormOf
Indicates that one occupation is a specific form, variant, or specialization of another, more general occupation.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.