Triple
T29316716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trappistine Convent |
E743398
|
entity |
| Predicate | productsSoldAt |
P191090
|
FINISHED |
| Object | onsite shop |
—
|
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: onsite shop | Statement: [Trappistine Convent, productsSoldAt, onsite shop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productsSoldAt Context triple: [Trappistine Convent, productsSoldAt, onsite shop]
-
A.
soldProducts
Indicates that an entity has sold certain products to another entity or in a particular context.
-
B.
soldProductType
Indicates that an entity has sold a product belonging to a specified product type.
-
C.
marketedProducts
Indicates that an entity promotes, sells, or otherwise brings specific products to market.
-
D.
plansSoldBy
Indicates that one entity is the seller or provider of plans that are purchased or obtained by another entity.
-
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. 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: April 28, 2026, 1:20 p.m.