Triple
T15464655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Monday Trade Days |
E371999
|
entity |
| Predicate | vendorCount |
P5785
|
FINISHED |
| Object | thousands of vendors at peak times |
—
|
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: thousands of vendors at peak times | Statement: [First Monday Trade Days, vendorCount, thousands of vendors at peak times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorCount Context triple: [First Monday Trade Days, vendorCount, thousands of vendors at peak times]
-
A.
vendorType
Indicates the classification or category of a vendor based on the type of goods or services they provide.
-
B.
dataVendor
Indicates a relationship where one entity serves as a provider or supplier of data to another entity.
-
C.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
D.
hasApproximateVendorCount
chosen
Indicates that an entity is associated with an estimated or non-exact number of vendors.
-
E.
eligibleVendors
Indicates that certain vendors meet the required criteria or conditions to be considered eligible for a specified purpose or process.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f680cec8190836a5ec841dee224 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.