Triple
T4599408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gold coin mint |
E100284
|
entity |
| Predicate | mayMarkWith |
P17363
|
FINISHED |
| Object | mint mark |
—
|
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: mint mark | Statement: [gold coin mint, mayMarkWith, mint mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayMarkWith Context triple: [gold coin mint, mayMarkWith, mint mark]
-
A.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
B.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
C.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
D.
mintMarkUsedOn
chosen
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
-
E.
marque
Indicates that one entity is the brand or make associated with another entity, such as a product, vehicle, or manufactured item.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59707f8c8190b8368f1de887ff2a |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.