Triple
T6328380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunar series coins |
E141914
|
entity |
| Predicate | isIssued |
P70880
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [Lunar series coins, isIssued, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIssued Context triple: [Lunar series coins, isIssued, annually]
-
A.
isIssuedFor
Indicates that something (such as a document, order, or item) has been formally created, authorized, or provided for a specific purpose, recipient, or use.
-
B.
isIssuedTo
Indicates that something, such as a document, credential, or item, has been formally given or assigned to a specific recipient.
-
C.
issuedWith
Indicates that one entity is formally provided, granted, or supplied together with another entity as part of the same issuance event.
-
D.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
E.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651197908190a30e504e2442d40f |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:29 p.m.