Triple
T37612145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seidel family (benefactors) |
E935810
|
entity |
| Predicate | benefactionType |
P189077
|
FINISHED |
| Object | school endowment |
—
|
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: school endowment | Statement: [Seidel family (benefactors), benefactionType, school endowment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefactionType Context triple: [Seidel family (benefactors), benefactionType, school endowment]
-
A.
beneficeType
Indicates the specific category or kind of benefice (ecclesiastical office or endowed church position) associated with an entity.
-
B.
benefactionLocation
Indicates the place or location where a benefaction (such as a gift, donation, or helpful act) is given, received, or takes effect.
-
C.
benefice
Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
-
D.
benefitsCategory
Indicates that one entity provides, falls under, or is associated with a particular category of benefits for another entity.
-
E.
benefactor
Indicates that one entity provides help, support, or resources to another, typically in a generous or supportive role.
- F. None of above. chosen
Provenance (4 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.