Triple
T12102750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens Mint |
E288228
|
entity |
| Predicate | productCharacteristic |
P103513
|
FINISHED |
| Object | high silver fineness |
—
|
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: high silver fineness | Statement: [Athens Mint, productCharacteristic, high silver fineness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productCharacteristic Context triple: [Athens Mint, productCharacteristic, high silver fineness]
-
A.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
B.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
C.
producerCharacteristic
Indicates a relationship where a producer is associated with a particular attribute, quality, or trait that characterizes them or their production.
-
D.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
E.
codeCharacteristic
Indicates that one piece of code possesses a specific property, feature, or quality in relation to another referenced aspect.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d9178814e081908f67e3846718530e |
completed | April 10, 2026, 3:30 p.m. |
Created at: April 8, 2026, 9:48 p.m.