Triple
T9840517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asbury University |
E239210
|
entity |
| Predicate | hasSpiritualLifeOffice |
P90279
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Asbury University, hasSpiritualLifeOffice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpiritualLifeOffice Context triple: [Asbury University, hasSpiritualLifeOffice, true]
-
A.
spiritualMinistry
Indicates that one entity provides religious or spiritual guidance, care, or services to another entity.
-
B.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
C.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
-
D.
hasLiturgicalLife
Indicates that an entity participates in or maintains practices, rituals, and rhythms associated with liturgical worship.
-
E.
inTheSpiritOf
Indicates that one entity acts, is created, or is characterized in a manner that follows the style, principles, or intent exemplified by another entity.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34c920c81909b56ed9936b15f9b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:33 p.m.