Triple
T4524306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit universities |
E103339
|
entity |
| Predicate | typicalCampusMinistry |
P29527
|
FINISHED |
| Object | Jesuit chaplaincy |
—
|
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: Jesuit chaplaincy | Statement: [Jesuit universities, typicalCampusMinistry, Jesuit chaplaincy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCampusMinistry Context triple: [Jesuit universities, typicalCampusMinistry, Jesuit chaplaincy]
-
A.
campusOrganization
Indicates that one entity is an organization that operates within, is based at, or is formally affiliated with a particular campus.
-
B.
campusLife
chosen
Indicates the overall experience, activities, and social environment associated with being part of a particular campus or educational institution.
-
C.
governsCampus
Indicates that one entity has administrative or authoritative control over the operations and policies of a campus.
-
D.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
-
E.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5773341c8190bf27745feb863575 |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.