Triple
T35184772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of the Roses |
E1015954
|
entity |
| Predicate | hasOrganizedApostolate |
P192857
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Our Lady of the Roses, hasOrganizedApostolate, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrganizedApostolate Context triple: [Our Lady of the Roses, hasOrganizedApostolate, yes]
-
A.
hasOrganised
Indicates that one entity has planned, coordinated, or arranged an event, activity, or group involving another entity.
-
B.
isApostolicWorkerIn
Indicates that a person serves or functions as an apostolic worker within a specified organization, community, or geographic area.
-
C.
hasApostolateType
chosen
Indicates that an entity is associated with or carries out a specific type of apostolic mission or ministry.
-
D.
isApostolicCongregation
Indicates that a religious community or congregation follows apostolic traditions, authority, or succession in its beliefs, practices, or governance.
-
E.
alsoOrganized
Indicates that the same entity was additionally responsible for organizing another related event, activity, or entity.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:02 p.m.