Triple
T33439549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian apparitions of 1877 |
E856322
|
entity |
| Predicate | hasVisionary |
P192512
|
FINISHED |
| Object | Justyna Szafryńska |
—
|
NE NERFINISHED |
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: Justyna Szafryńska | Statement: [Marian apparitions of 1877, hasVisionary, Justyna Szafryńska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisionary Context triple: [Marian apparitions of 1877, hasVisionary, Justyna Szafryńska]
-
A.
hasVisionOf
Indicates that one entity perceives, imagines, or foresees another entity or scenario, typically in a mental, prophetic, or visualized form.
-
B.
hasMainVisionary
Indicates that one entity serves as the primary creative or strategic visionary responsible for guiding or shaping another entity.
-
C.
containsVisionOf
Indicates that one entity includes, depicts, or embodies a visual representation or image of another entity.
-
D.
visionary
Indicates that an entity is recognized for having original, forward-thinking ideas or plans that anticipate future developments.
-
E.
visionaryOf
Indicates that one entity is the original conceiver or driving visionary behind the creation, direction, or concept of another entity.
- F. None of above. chosen
Provenance (4 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: May 1, 2026, 1:37 a.m.