Triple
T13489703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Investment Fund |
E318600
|
entity |
| Predicate | financialIntermediaryType |
P32144
|
FINISHED |
| Object | banks |
—
|
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: banks | Statement: [European Investment Fund, financialIntermediaryType, banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialIntermediaryType Context triple: [European Investment Fund, financialIntermediaryType, banks]
-
A.
intermediaryType
chosen
Indicates the specific role or category of intermediary involved in facilitating the relationship or transaction between entities.
-
B.
courtierOf
Indicates that one entity serves as a courtier in the court of another, typically a monarch or noble.
-
C.
alsoProvidesFinanceIn
Indicates that an entity, in addition to other roles or services, supplies financial support or funding within a specified context or location.
-
D.
lenderType
Indicates the classification or category of the lender involved in a lending relationship (e.g., bank, individual, institution).
-
E.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3cbe2081908c6792362c67c8f1 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.