Triple
T3172367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Kazan |
E66382
|
entity |
| Predicate | discoveryTraditionallyDatedToYear |
P31438
|
FINISHED |
| Object | 1579 |
—
|
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: 1579 | Statement: [Our Lady of Kazan, discoveryTraditionallyDatedToYear, 1579]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryTraditionallyDatedToYear Context triple: [Our Lady of Kazan, discoveryTraditionallyDatedToYear, 1579]
-
A.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
B.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
C.
discoveryYear
Indicates the calendar year in which something was first discovered or identified.
-
D.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada66da23c81908f063b44b48b1e53 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.