Triple
T6304270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontefract |
E141332
|
entity |
| Predicate | hasTraditionalConfectionery |
P19423
|
FINISHED |
| Object | liquorice |
—
|
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: liquorice | Statement: [Pontefract, hasTraditionalConfectionery, liquorice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalConfectionery Context triple: [Pontefract, hasTraditionalConfectionery, liquorice]
-
A.
traditionalSweet
Indicates that something is a sweet food or dessert prepared according to long-established customs or cultural traditions.
-
B.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
-
C.
hasSugarFreeVariant
Indicates that an item has a corresponding version or option that is formulated without sugar.
-
D.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
E.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645f26a881909d5746151c0843cc |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.