Triple
T6388425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Seminary of St. Peter, Wigratzbad, Germany |
E143757
|
entity |
| Predicate | hasCommunityLife |
P70317
|
FINISHED |
| Object | common prayer and liturgy |
—
|
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: common prayer and liturgy | Statement: [International Seminary of St. Peter, Wigratzbad, Germany, hasCommunityLife, common prayer and liturgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityLife Context triple: [International Seminary of St. Peter, Wigratzbad, Germany, hasCommunityLife, common prayer and liturgy]
-
A.
hasLocalCommunities
Indicates that an entity is associated with or contains smaller, localized community groups within a specific area or region.
-
B.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
C.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
D.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
E.
hasPlannedCommunity
Indicates that an entity is associated with or contains a community that has been intentionally designed and organized according to a specific development plan.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686b4f34819088ff07185b34e536 |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.