Triple
T28408392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeginetan silver staters |
E719599
|
entity |
| Predicate | earliestIssuesDateTo |
P64188
|
FINISHED |
| Object | circa 550 BCE (approximate) |
—
|
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: circa 550 BCE (approximate) | Statement: [Aeginetan silver staters, earliestIssuesDateTo, circa 550 BCE (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestIssuesDateTo Context triple: [Aeginetan silver staters, earliestIssuesDateTo, circa 550 BCE (approximate)]
-
A.
earliestDate
chosen
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
B.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
C.
dateOfFirstCriticality
Indicates the date on which a nuclear reactor or system first achieved a self-sustaining nuclear chain reaction (first became critical).
-
D.
earliestDocumentsDate
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
-
E.
firstIssuedOnFormat
Indicates the specific date format used to represent when something was first issued.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 1:25 a.m.