Triple
T9366557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassanian drahm |
E225414
|
entity |
| Predicate | circulatedFromCentury |
P71372
|
FINISHED |
| Object | 3rd century |
—
|
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: 3rd century | Statement: [Sassanian drahm, circulatedFromCentury, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulatedFromCentury Context triple: [Sassanian drahm, circulatedFromCentury, 3rd century]
-
A.
circulatedDuring
chosen
Indicates that something was in active distribution or use throughout a specified time period or event.
-
B.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
C.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
D.
ruledFromCentury
Indicates that a ruling or governance relationship is associated with a specific century during which it took place.
-
E.
attestedFromCentury
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5042c89c8190994b12cf7600c366 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.