Triple
T22540608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Charles Borromeo Seminary |
E557277
|
entity |
| Predicate | hasCampusActivity |
P95727
|
FINISHED |
| Object | liturgical worship |
—
|
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: liturgical worship | Statement: [St. Charles Borromeo Seminary, hasCampusActivity, liturgical worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampusActivity Context triple: [St. Charles Borromeo Seminary, hasCampusActivity, liturgical worship]
-
A.
hasCampusCharacter
Indicates that an institution possesses a particular overall campus atmosphere, style, or defining quality.
-
B.
hasOnsiteActivity
chosen
Indicates that an entity conducts or participates in activities that physically take place at a specific site or location.
-
C.
hasCampusState
Indicates that an institution’s campus is located within a specified state or state-level administrative region.
-
D.
hasCampusCommunity
Indicates that an institution or location possesses an associated campus-based community or group of people connected to it.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f3196fc819098deffb0c7932ccc |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.