Triple
T7384299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karelian pies |
E170341
|
entity |
| Predicate | isCommonlySoldAt |
P51662
|
FINISHED |
| Object | Finnish bakeries |
—
|
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: Finnish bakeries | Statement: [Karelian pies, isCommonlySoldAt, Finnish bakeries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlySoldAt Context triple: [Karelian pies, isCommonlySoldAt, Finnish bakeries]
-
A.
isSoldIn
chosen
Indicates that a product or item is available for purchase within a specified location, market, or sales channel.
-
B.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
C.
notSoldIn
Indicates that a product or item is unavailable for purchase within a specified market, region, or sales channel.
-
D.
soldAt
Indicates that a product or item is offered for sale at a particular location, venue, or outlet.
-
E.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1efe1308190b96eefbff56140be |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.