Triple
T18563939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inscriptional Parthian |
E453714
|
entity |
| Predicate | yearOfStandardization |
P132519
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Inscriptional Parthian, yearOfStandardization, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfStandardization Context triple: [Inscriptional Parthian, yearOfStandardization, 2009]
-
A.
timePeriodOfStandardization
Indicates the time span during which a particular standard was formally established or in effect.
-
B.
wasGraduallyStandardizedIn
Indicates that something became standardized or uniform within a particular context through a gradual, step-by-step process over time.
-
C.
laterStandardization
Indicates that one entity becomes standardized or formally established at a later time than another entity.
-
D.
goldStandardAdoptionYear
Indicates the year in which a particular gold standard was officially adopted or implemented.
-
E.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:42 a.m.