Triple
T38331922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilgoris |
E1037844
|
entity |
| Predicate | hasFinancialService |
P525
|
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: [Kilgoris, hasFinancialService, banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinancialService Context triple: [Kilgoris, hasFinancialService, banks]
-
A.
hasBanking
Indicates that one entity provides or is associated with banking services or facilities for another entity.
-
B.
hasFinancialInstitution
chosen
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
-
C.
hasFinancialFunction
Indicates that an entity performs, supports, or is responsible for a specific financial role, operation, or service in relation to another entity.
-
D.
hasHighBanking
Indicates that an entity is associated with a banking institution that has a high or elevated status, capacity, or performance level.
-
E.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: May 3, 2026, 4:30 p.m.