Triple
T35594452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert of Mainz |
E1028587
|
entity |
| Predicate | owedDebtTo |
P52432
|
FINISHED |
| Object | Fugger banking house |
—
|
NE NERFINISHED |
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: Fugger banking house | Statement: [Albert of Mainz, owedDebtTo, Fugger banking house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: owedDebtTo Context triple: [Albert of Mainz, owedDebtTo, Fugger banking house]
-
A.
owedLifeDebtTo
Indicates that one entity is bound by a significant obligation or duty to another entity, typically as repayment for having their life saved or preserved.
-
B.
debt
Indicates that one entity owes money or an obligation to another entity, typically to be repaid under agreed conditions.
-
C.
typeOfDebtManaged
Indicates the specific category or kind of debt that is being handled or overseen in the described relationship or context.
-
D.
viewOnDebt
Indicates a stance, opinion, or attitude that one entity holds regarding debt or indebtedness.
-
E.
owedMoneyTo
chosen
Indicates that one entity has a financial obligation or debt that must be paid to another entity.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.