Triple
T37666081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snow Kingdom |
E937821
|
entity |
| Predicate | hasRegionalCoinShape |
P202317
|
FINISHED |
| Object | snowflake |
—
|
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: snowflake | Statement: [Snow Kingdom, hasRegionalCoinShape, snowflake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalCoinShape Context triple: [Snow Kingdom, hasRegionalCoinShape, snowflake]
-
A.
regionalCoinShape
chosen
Indicates that the coin has a shape characteristic of or specific to a particular geographic region.
-
B.
hasRegionalStone
Indicates that something possesses or is associated with a characteristic stone specific to a particular region.
-
C.
hasBillShape
Indicates that one entity has a bill whose shape matches the specified form or category.
-
D.
isLegalTenderFor
Indicates that a particular currency or form of money is officially recognized by a governing authority as valid payment for debts and financial transactions within a specified jurisdiction.
-
E.
coinageType
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.