Triple
T4344627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Stability Mechanism |
E97869
|
entity |
| Predicate | lendingCapacity |
P14460
|
FINISHED |
| Object | €500 billion |
—
|
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: €500 billion | Statement: [European Stability Mechanism, lendingCapacity, €500 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lendingCapacity Context triple: [European Stability Mechanism, lendingCapacity, €500 billion]
-
A.
lendingArm
Indicates that one entity provides financial support or resources to another, typically in the form of a loan or credit.
-
B.
loanLimitType
Indicates the category or rule that defines how a loan’s maximum allowable amount or terms are limited.
-
C.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
E.
offersCapacityRange
Indicates that an entity provides or makes available a service, product, or resource whose capacity is specified as a range between a minimum and maximum value.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3518aa5cc8190b50f47b1070715fe |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.