Triple
T934890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicene Christianity |
E20172
|
entity |
| Predicate | historicalOriginYear |
P9428
|
FINISHED |
| Object | 325 |
—
|
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: 325 | Statement: [Nicene Christianity, historicalOriginYear, 325]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalOriginYear Context triple: [Nicene Christianity, historicalOriginYear, 325]
-
A.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
originYear
chosen
Indicates the year in which something first originated, was created, or began.
-
C.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
D.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
E.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b363ea5c819098ec1d87f785bad4 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.