Triple
T13331775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwibbogen |
E317590
|
entity |
| Predicate | isHandcrafted |
P77076
|
FINISHED |
| Object | often |
—
|
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: often | Statement: [Schwibbogen, isHandcrafted, often]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHandcrafted Context triple: [Schwibbogen, isHandcrafted, often]
-
A.
isHandmade
chosen
Indicates that an object has been crafted or produced by hand rather than by automated or industrial processes.
-
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.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
D.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
-
E.
isHandPicked
Indicates that something or someone has been personally selected with deliberate care or preference, rather than chosen randomly or automatically.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992fffa0819086610ae3bed2e2f9 |
completed | April 11, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.