Triple
T18747177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homerite Kingdom |
E458433
|
entity |
| Predicate | adoptedReligionDate |
P35940
|
FINISHED |
| Object | late 4th century CE |
—
|
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: late 4th century CE | Statement: [Homerite Kingdom, adoptedReligionDate, late 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedReligionDate Context triple: [Homerite Kingdom, adoptedReligionDate, late 4th century CE]
-
A.
dateOfChristianization
chosen
Indicates the date on which a person, group, or place was converted to Christianity or formally adopted the Christian faith.
-
B.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
C.
religiousConversionPeriod
Indicates the time span during which an entity undergoes or is involved in a process of religious conversion.
-
D.
dateAdopted
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
E.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e576936cf08190b3c0d2f4e8a616fc |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.