Triple
T24941870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Nazarene University |
E623478
|
entity |
| Predicate | hasCampusMinistries |
P159397
|
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: [Northwest Nazarene University, hasCampusMinistries, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampusMinistries Context triple: [Northwest Nazarene University, hasCampusMinistries, yes]
-
A.
campusOrganization
Indicates that one entity is an organization that operates within, is based at, or is formally affiliated with a particular campus.
-
B.
hasStudentOrganization
Indicates that an entity (such as an institution or department) is associated with or hosts a particular student organization.
-
C.
hasCampusCommunity
Indicates that an institution or location possesses an associated campus-based community or group of people connected to it.
-
D.
governsCampus
Indicates that one entity has administrative or authoritative control over the operations and policies of a campus.
-
E.
hasCampusState
Indicates that an institution’s campus is located within a specified state or state-level administrative region.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f584f07b648190aee894c1d5320bc3 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 18, 2026, 5:30 a.m.