Triple
T4285985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kendal |
E97268
|
entity |
| Predicate | mintCakeAssociatedWith |
P55215
|
FINISHED |
| Object | mountaineering |
—
|
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: mountaineering | Statement: [Kendal, mintCakeAssociatedWith, mountaineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintCakeAssociatedWith Context triple: [Kendal, mintCakeAssociatedWith, mountaineering]
-
A.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
-
B.
associatedWithRoyalty
Indicates a relationship in which an entity has a notable connection to royalty, such as through lineage, service, patronage, or symbolic affiliation.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
nativeTokenOf
Indicates that a given token is the primary, built-in (native) currency or asset of a specified blockchain or platform.
-
E.
mintedAt
Indicates the specific time or block at which a digital asset or token was created (minted) on a blockchain.
- 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.