Triple
T8822244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Vernon Marketplace |
E209932
|
entity |
| Predicate | vendorType |
P84821
|
FINISHED |
| Object | local vendors |
—
|
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: local vendors | Statement: [Mount Vernon Marketplace, vendorType, local vendors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorType Context triple: [Mount Vernon Marketplace, vendorType, local vendors]
-
A.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
B.
vendorDesignation
Indicates that one entity assigns or recognizes a specific vendor status, label, or role for another entity within a business or procurement context.
-
C.
vendorSpecificTo
Indicates that something is tailored, restricted, or applicable only to a particular vendor or supplier, and not generally applicable across others.
-
D.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
E.
dataVendorName
Indicates the name or identifier of the vendor that supplies or provides the data.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc602ed87c8190ab772e5cbb2da68d |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:46 p.m.