Triple
T15422851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Virginia University |
E369426
|
entity |
| Predicate | faithSupportive |
P97986
|
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: [Southern Virginia University, faithSupportive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faithSupportive Context triple: [Southern Virginia University, faithSupportive, true]
-
A.
beliefEncouragedBy
Indicates that one entity’s belief is supported, strengthened, or promoted as a result of influence, actions, or encouragement from another entity.
-
B.
religiousSupportType
chosen
Indicates the type or form of support provided or received in a religious or faith-based context.
-
C.
supportedCreed
Indicates that one entity endorsed, upheld, or actively promoted a particular belief system, doctrine, or set of principles associated with another entity.
-
D.
supportedMinistryIn
Indicates that an entity provided support to a ministry operating within a specified location or jurisdiction.
-
E.
religiousMotivation
Indicates that an action, decision, or relationship is driven or significantly influenced by religious beliefs, values, or obligations.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec032548190840b558dde6057c7 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.