Triple
T36992901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | گریگورین کیلنڈر |
E915152
|
entity |
| Predicate | متعارف_کرانے_کی_تاریخ |
P187258
|
FINISHED |
| Object | ۱۵ اکتوبر ۱۵۸۲ |
—
|
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: ۱۵ اکتوبر ۱۵۸۲ | Statement: [گریگورین کیلنڈر, متعارف_کرانے_کی_تاریخ, ۱۵ اکتوبر ۱۵۸۲]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: متعارف_کرانے_کی_تاریخ Context triple: [گریگورین کیلنڈر, متعارف_کرانے_کی_تاریخ, ۱۵ اکتوبر ۱۵۸۲]
-
A.
traditionallyDated
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
B.
chronicledBy
Indicates that something is documented, recorded, or described in detail by a particular source, author, or record.
-
C.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
D.
historicallyFoundOn
Indicates that something was typically or commonly located on or associated with something else during a past historical period.
-
E.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.