Triple
T20061162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bpifrance |
E499476
|
entity |
| Predicate | guaranteeFunction |
P32141
|
FINISHED |
| Object | guarantees bank loans to businesses |
—
|
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: guarantees bank loans to businesses | Statement: [Bpifrance, guaranteeFunction, guarantees bank loans to businesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guaranteeFunction Context triple: [Bpifrance, guaranteeFunction, guarantees bank loans to businesses]
-
A.
guaranteedFor
Indicates that one entity provides an assurance or warranty that remains valid for another entity over a specified period or under certain conditions.
-
B.
guaranteeProvider
chosen
Indicates that one entity serves as the party that provides or issues a guarantee for another entity or obligation.
-
C.
guaranteeScope
Indicates that one entity defines or limits the extent, conditions, or coverage under which a guarantee provided by another entity is valid.
-
D.
mayGuarantee
Indicates that one entity has the potential or authority to provide a guarantee for another entity or outcome.
-
E.
guaranteeStatus
Indicates the current state or condition of a guarantee associated with an entity or agreement.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6637601dc8190a07fc20844093cb7 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.