Triple
T18891146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brite Divinity School |
E462087
|
entity |
| Predicate | hasAlumniWorkingAs |
P89630
|
FINISHED |
| Object | pastors |
—
|
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: pastors | Statement: [Brite Divinity School, hasAlumniWorkingAs, pastors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlumniWorkingAs Context triple: [Brite Divinity School, hasAlumniWorkingAs, pastors]
-
A.
hasAlumni
Indicates that an institution or organization is associated with individuals who formerly attended or graduated from it.
-
B.
hasProfessionalAlumni
chosen
Indicates that an institution or organization has alumni who have gone on to work in a specified profession or professional field.
-
C.
hasAlumnusPosition
Indicates that an individual holds or has held a position or role as an alumnus of a particular institution or organization.
-
D.
hasAlumniOutcome
Indicates that an entity has a specific outcome or post-completion status associated with its alumni.
-
E.
hasAlumniField
Indicates a relationship where an entity is associated with a specific field or area of study in which its alumni specialized or graduated.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47ab34c8190bfb69444a5263538 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.