Triple
T23563258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnsley Market |
E579298
|
entity |
| Predicate | typicalVendorType |
P17473
|
FINISHED |
| Object | independent stallholders |
—
|
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: independent stallholders | Statement: [Barnsley Market, typicalVendorType, independent stallholders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVendorType Context triple: [Barnsley Market, typicalVendorType, independent stallholders]
-
A.
vendorType
Indicates the classification or category of a vendor based on the type of goods or services they provide.
-
B.
technologyVendor
Indicates that one entity serves as the provider or supplier of technology products or services to another entity.
-
C.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
D.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
E.
typicalProvider
chosen
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6a02208190b7d35c4e5da67a44 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:31 p.m.