Triple
T4344718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Financial Stability Facility |
E97871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special purpose vehicle |
C12318
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: special purpose vehicle Context triple: [European Financial Stability Facility, instanceOf, special purpose vehicle]
-
A.
special purpose entity
chosen
A special purpose entity is a legally separate organization created by a parent company to isolate financial risk, hold specific assets or liabilities, or conduct narrowly defined activities, often for financing or regulatory purposes.
-
B.
sport utility vehicle
A sport utility vehicle is a versatile passenger vehicle that combines elements of on-road cars and off-road trucks, typically offering higher ground clearance, spacious interiors, and optional all-wheel or four-wheel drive for varied driving conditions.
-
C.
special-purpose money
Special-purpose money is a form of currency or value token that is restricted to specific uses, transactions, or contexts rather than serving as a general medium of exchange.
-
D.
commercial vehicle manufacturer
A commercial vehicle manufacturer is a company that designs, produces, and sells vehicles intended primarily for business use, such as trucks, buses, and vans, to transport goods or passengers.
-
E.
commercial vehicle brand
A commercial vehicle brand is a company or trademark that designs, manufactures, and markets vehicles primarily intended for business use, such as transporting goods, passengers, or providing specialized services.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 12, 2026, 11:15 p.m.