Triple
T4285986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kendal |
E97268
|
entity |
| Predicate | mintCakeUsedOn |
P55216
|
FINISHED |
| Object | Everest expeditions |
—
|
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: Everest expeditions | Statement: [Kendal, mintCakeUsedOn, Everest expeditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintCakeUsedOn Context triple: [Kendal, mintCakeUsedOn, Everest expeditions]
-
A.
madeWith
Indicates that one entity is created, produced, or constructed using another entity as a material, ingredient, or component.
-
B.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
-
C.
mintMarkUsedOn
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
-
D.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
E.
isBaked
Indicates that an entity has undergone a baking process, typically by being cooked with dry heat in an oven or similar environment.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3505d23d88190a638f2cc2acee9ee |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.