Triple
T2389920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco-Czechoslovak alliance |
E48916
|
entity |
| Predicate | diplomaticCharacter |
P38141
|
FINISHED |
| Object | bilateral |
—
|
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: bilateral | Statement: [Franco-Czechoslovak alliance, diplomaticCharacter, bilateral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticCharacter Context triple: [Franco-Czechoslovak alliance, diplomaticCharacter, bilateral]
-
A.
diplomaticRole
Indicates that an entity holds or has held an official diplomatic position or function in relation to another entity or context.
-
B.
typeOfDiplomaticRole
Indicates the specific kind or category of diplomatic position or function that an entity holds in relation to another.
-
C.
involvesDiplomat
Indicates that a situation, event, or interaction includes the participation or presence of a diplomat as a relevant party.
-
D.
involvedDiplomat
Indicates that a diplomat participated in, was associated with, or played a role in a specified event, interaction, or situation.
-
E.
diplomaticPost
Indicates that an entity holds or is assigned to an official diplomatic position or mission representing one state or organization to another.
- F. None of above. chosen
Provenance (4 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7de1478819082238e8b8f88ed06 |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.