Triple
T12102727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens Mint |
E288228
|
entity |
| Predicate | inscriptionFeatured |
P34998
|
FINISHED |
| Object | ΑΘΕ (abbreviation for Athenians) |
—
|
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: ΑΘΕ (abbreviation for Athenians) | Statement: [Athens Mint, inscriptionFeatured, ΑΘΕ (abbreviation for Athenians)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionFeatured Context triple: [Athens Mint, inscriptionFeatured, ΑΘΕ (abbreviation for Athenians)]
-
A.
inscriptionFeature
chosen
Indicates that one entity bears or contains an inscribed element or marking that is treated as a notable feature in relation to another entity.
-
B.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
C.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
D.
inscriptionMaterial
Indicates the material substance on which an inscription is made or carved.
-
E.
inscriptionStatus
Indicates the current state or condition of an inscription, such as whether it has been created, verified, updated, or removed.
- 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_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. |
Created at: April 8, 2026, 9:48 p.m.