Triple
T36030451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Panier historic district |
E1042242
|
entity |
| Predicate | localProduct |
P104011
|
FINISHED |
| Object | artisan soaps |
—
|
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: artisan soaps | Statement: [Le Panier historic district, localProduct, artisan soaps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localProduct Context triple: [Le Panier historic district, localProduct, artisan soaps]
-
A.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
-
B.
providedProduct
Indicates that one entity has supplied or made available a particular product to another entity.
-
C.
vendorProductOf
chosen
Indicates that a product is offered or supplied by a particular vendor.
-
D.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
E.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:07 p.m.