Triple
T14715647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perinthus |
E345671
|
entity |
| Predicate | laterCurrencyUsed |
P26139
|
FINISHED |
| Object | Roman coinage |
—
|
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: Roman coinage | Statement: [Perinthus, laterCurrencyUsed, Roman coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCurrencyUsed Context triple: [Perinthus, laterCurrencyUsed, Roman coinage]
-
A.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
-
B.
successorCurrenciesUsed
chosen
Indicates that the currencies referenced have been used as successor currencies replacing a previous currency in use.
-
C.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
D.
successorCurrencyOf
Indicates that one currency has replaced another as the official or primary currency in use.
-
E.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98513b081908b230f6ac79c72ad |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.