Triple
T34397592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Amorium |
E882874
|
entity |
| Predicate | yearInChristianEra |
P61142
|
FINISHED |
| Object | 838 |
—
|
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: 838 | Statement: [Siege of Amorium, yearInChristianEra, 838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearInChristianEra Context triple: [Siege of Amorium, yearInChristianEra, 838]
-
A.
تاريخ_الإنشاء_ميلادي
Indicates the Gregorian calendar date on which something was created or established.
-
B.
yearCirca
Indicates that the associated year is approximate or uncertain rather than exact.
-
C.
BuddhistEraYear
Indicates that a given year value is expressed according to the Buddhist Era (BE) calendar system rather than another calendar such as the Gregorian year.
-
D.
yearInGregorianCalendar
chosen
Indicates that a specified year is measured according to the Gregorian calendar system.
-
E.
dateOfEcumenicalNumbering
Indicates the date on which an event, council, or item is assigned its official ecumenical sequence or numbering within a recognized series.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.