Triple
T34381817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Knock |
E882458
|
entity |
| Predicate | hasVisionaryType |
P192938
|
FINISHED |
| Object | lay witnesses |
—
|
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: lay witnesses | Statement: [Our Lady of Knock, hasVisionaryType, lay witnesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisionaryType Context triple: [Our Lady of Knock, hasVisionaryType, lay witnesses]
-
A.
hasVisionary
Indicates that an entity is associated with or guided by a visionary individual or visionary concept.
-
B.
hasMainVisionary
Indicates that one entity serves as the primary creative or strategic visionary responsible for guiding or shaping another entity.
-
C.
hasVisionOf
Indicates that one entity perceives, imagines, or foresees another entity or scenario, typically in a mental, prophetic, or visualized form.
-
D.
containsVisionOf
Indicates that one entity includes, depicts, or embodies a visual representation or image of another entity.
-
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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 1, 2026, 1:59 a.m.