Triple
T33873137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Film Capital Europe Funds |
E868276
|
entity |
| Predicate | investmentDomain |
P45042
|
FINISHED |
| Object | feature films |
—
|
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: feature films | Statement: [Film Capital Europe Funds, investmentDomain, feature films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investmentDomain Context triple: [Film Capital Europe Funds, investmentDomain, feature films]
-
A.
investment
Indicates a relationship where one party allocates resources (such as money, time, or effort) into something with the expectation of future benefit or return.
-
B.
investmentScope
chosen
Indicates the range or boundaries of activities, assets, or sectors that an investment is intended or allowed to cover.
-
C.
vestments
Indicates that one entity is wearing or is ceremonially clothed in special religious or official garments associated with a role or office.
-
D.
investmentType
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
E.
investmentSource
Indicates that one entity serves as the origin or provider of investment funds or capital for another entity.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:47 a.m.