Triple
T9840492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asbury University |
E239210
|
entity |
| Predicate | hasReligiousLifePrograms |
P80379
|
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, hasReligiousLifePrograms, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousLifePrograms Context triple: [Asbury University, hasReligiousLifePrograms, true]
-
A.
hasReligiousProgramming
chosen
Indicates that an entity provides, features, or includes content or activities related to religious themes, practices, or teachings.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
languageOfReligiousLife
Indicates the language primarily used in the religious practices, rituals, or spiritual life associated with an entity.
-
D.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
E.
hasReligiousForms
Indicates that an entity possesses or is associated with specific religious expressions, practices, or organizational structures.
- 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_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. |
Created at: March 30, 2026, 8:33 p.m.