Triple
T37341877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin of the Pillar |
E927059
|
entity |
| Predicate | apparitionDateTradition |
P37101
|
FINISHED |
| Object | 1st century |
—
|
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: 1st century | Statement: [Virgin of the Pillar, apparitionDateTradition, 1st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apparitionDateTradition Context triple: [Virgin of the Pillar, apparitionDateTradition, 1st century]
-
A.
apparitionsDate
chosen
Indicates the date on which the apparitions are reported or believed to have occurred.
-
B.
apparitionsType
Indicates that one entity is a specific type or category of apparition in relation to another entity.
-
C.
apparitionsRecognizedBy
Indicates that certain apparitions are acknowledged, identified, or accepted as genuine by a particular person, group, or authority.
-
D.
apparitionsYear
Indicates the year in which the apparitions or appearances associated with an entity took place.
-
E.
associatedWithApparition
Indicates a relationship where something is linked or connected to an apparition, such as being caused by, accompanying, or characterizing that apparition.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.