Triple
T3486186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lane Theological Seminary |
E73610
|
entity |
| Predicate | primaryDegree |
P6
|
FINISHED |
| Object | Bachelor of Divinity |
—
|
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: Bachelor of Divinity | Statement: [Lane Theological Seminary, primaryDegree, Bachelor of Divinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDegree Context triple: [Lane Theological Seminary, primaryDegree, Bachelor of Divinity]
-
A.
primarySchool
Indicates that one entity serves as the primary (elementary) school attended by, associated with, or designated for the other entity.
-
B.
academicDegree
chosen
Indicates that an entity holds or has been awarded a specific academic degree.
-
C.
typicalDegree
Indicates the usual or characteristic level, intensity, or extent to which something holds or applies in a given context.
-
D.
primaryIntake
Indicates that one entity serves as the main or first point of intake, reception, or admission for another entity.
-
E.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9059f881908f9cbe544365c8df |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.