Triple
T12898548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech–German relations |
E308555
|
entity |
| Predicate | Czech–German Future Fund |
P33009
|
FINISHED |
| Object | supports joint projects and reconciliation |
—
|
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: supports joint projects and reconciliation | Statement: [Czech–German relations, Czech–German Future Fund, supports joint projects and reconciliation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Czech–German Future Fund Context triple: [Czech–German relations, Czech–German Future Fund, supports joint projects and reconciliation]
-
A.
czechName
Indicates that an entity has a name in the Czech language, specifying the Czech-language form of its name.
-
B.
MunichAgreementSignatory
Indicates that an entity was a formal signatory to the Munich Agreement.
-
C.
funderOf
chosen
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
D.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
E.
monetaryUnionPartner
Indicates that two entities are members of the same monetary union, sharing a common currency or coordinated monetary policy.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717f3fc48190b61c8f6f36cd0725 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.