Triple
T23350773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brewster & Co. |
E592000
|
entity |
| Predicate | craftsmanshipLevel |
P151982
|
FINISHED |
| Object | hand-built |
—
|
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-built | Statement: [Brewster & Co., craftsmanshipLevel, hand-built]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftsmanshipLevel Context triple: [Brewster & Co., craftsmanshipLevel, hand-built]
-
A.
craftsmanshipReputation
Indicates the recognized quality and reliability of an entity’s workmanship as perceived by others.
-
B.
hasCraftsman
Indicates that one entity serves as the craftsman, maker, or artisan responsible for creating, building, or crafting another entity.
-
C.
craftSpecialty
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
D.
virtuosityLevel
Indicates the degree or extent of exceptional skill or mastery demonstrated in performing an action or activity.
-
E.
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.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a1401748190b77df0a45c2aeebf |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:19 p.m.