Triple
T5650184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent’s Park College, Oxford |
E124483
|
entity |
| Predicate | hasHistoricFoundation |
P1614
|
FINISHED |
| Object | Baptist theological training |
—
|
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: Baptist theological training | Statement: [Regent’s Park College, Oxford, hasHistoricFoundation, Baptist theological training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricFoundation Context triple: [Regent’s Park College, Oxford, hasHistoricFoundation, Baptist theological training]
-
A.
hasHistoricalOrigin
chosen
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
B.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
C.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
-
D.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
E.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d4ca788190b20168b20cb1d030 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.