Triple
T4629481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christendom College |
E101176
|
entity |
| Predicate | studentLifeFeature |
P29527
|
FINISHED |
| Object | strong Catholic campus culture |
—
|
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: strong Catholic campus culture | Statement: [Christendom College, studentLifeFeature, strong Catholic campus culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentLifeFeature Context triple: [Christendom College, studentLifeFeature, strong Catholic campus culture]
-
A.
campusLife
chosen
Indicates the overall experience, activities, and social environment associated with being part of a particular campus or educational institution.
-
B.
featuresInstitution
Indicates that one entity includes, presents, or highlights an institution as a notable component or participant.
-
C.
universityCharacteristic
Indicates that a specified characteristic, quality, or attribute is associated with a particular university.
-
D.
studentBodyFocus
Indicates that the primary attention, concern, or efforts are directed toward the student body as a whole.
-
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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a316ef48190831970ec914cf5a2 |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.