Triple
T5639058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham gun trade |
E124219
|
entity |
| Predicate | usedProductionSystem |
P10569
|
FINISHED |
| Object | workshop-based manufacture |
—
|
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: workshop-based manufacture | Statement: [Birmingham gun trade, usedProductionSystem, workshop-based manufacture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProductionSystem Context triple: [Birmingham gun trade, usedProductionSystem, workshop-based manufacture]
-
A.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
B.
fromProduction
Indicates that something originates from, is derived from, or is produced by a particular production process, source, or facility.
-
C.
hasMajorProductionSystem
chosen
Indicates that an entity primarily operates, utilizes, or is characterized by a particular major production system.
-
D.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
E.
usesProductionStyle
Indicates that one entity creates, presents, or operates another entity using a particular production style or method.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c02283bb248190b29ac6255c78c5ec |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.