Triple
T20292575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensign College |
E510062
|
entity |
| Predicate | hasReligiousInstruction |
P137217
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ensign College, hasReligiousInstruction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousInstruction Context triple: [Ensign College, hasReligiousInstruction, yes]
-
A.
religiousEducationStatus
Indicates the type or state of a person's involvement in religious education (e.g., whether and how they are receiving or have received religious instruction).
-
B.
usedForReligiousEducation
Indicates that something is employed as a means or resource for teaching, learning, or instruction in religious beliefs, practices, or traditions.
-
C.
offersReligiousEducation
chosen
Indicates that one entity provides or makes available instruction or educational programs related to religion to another entity.
-
D.
hasReligiousParent
Indicates that an entity has a parent who is associated with or practices a particular religion.
-
E.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677024de08190bfa54ae26b5486d1 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:12 a.m.