Triple
T23663624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontefract cake |
E584516
|
entity |
| Predicate | typicalStampMotif |
P41002
|
FINISHED |
| Object | castle design |
—
|
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: castle design | Statement: [Pontefract cake, typicalStampMotif, castle design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStampMotif Context triple: [Pontefract cake, typicalStampMotif, castle design]
-
A.
stampType
Indicates the specific category or classification of a stamp associated with an entity or transaction.
-
B.
featuresMotif
chosen
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
C.
maskPattern
Indicates a relationship where one entity serves as a masking template or pattern that determines which parts or aspects of another entity are revealed, hidden, or transformed.
-
D.
traditionalMotif
Indicates that something incorporates, represents, or is characterized by a motif rooted in established cultural or historical traditions.
-
E.
transformationMotif
Indicates a recurring pattern or theme in which one entity undergoes a change in form, state, or identity in relation to another.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40a1284819087cd29c9c390549d |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.