Triple
T285811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine the Great |
E5881
|
entity |
| Predicate | solidusIntroductionDate |
P4201
|
FINISHED |
| Object | c. 312–313 |
—
|
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: c. 312–313 | Statement: [Constantine the Great, solidusIntroductionDate, c. 312–313]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solidusIntroductionDate Context triple: [Constantine the Great, solidusIntroductionDate, c. 312–313]
-
A.
inceptionDate
chosen
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
D.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
E.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.