Triple
T8199706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Wave |
E191536
|
entity |
| Predicate | universityReligiousAffiliation |
P45
|
FINISHED |
| Object | nonsectarian |
—
|
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: nonsectarian | Statement: [Green Wave, universityReligiousAffiliation, nonsectarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universityReligiousAffiliation Context triple: [Green Wave, universityReligiousAffiliation, nonsectarian]
-
A.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
B.
associatedSchoolOfReligion
Indicates that an entity is connected with or belongs to a particular school or tradition within a religion.
-
C.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
D.
hasTheologicalFacultyAt
Indicates that an institution possesses or hosts a theological faculty at a specified location or campus.
-
E.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df565dc819099537fc06b694b40 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.