Triple
T32626685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bücker Bü 181 |
E834076
|
entity |
| Predicate | postwarDesignationInCzechoslovakia |
P123285
|
FINISHED |
| Object | Zlín C-6 |
—
|
NE NERFINISHED |
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: Zlín C-6 | Statement: [Bücker Bü 181, postwarDesignationInCzechoslovakia, Zlín C-6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postwarDesignationInCzechoslovakia Context triple: [Bücker Bü 181, postwarDesignationInCzechoslovakia, Zlín C-6]
-
A.
timeUnderCzechoslovakia
Indicates that the subject entity existed or was in effect during the historical period when Czechoslovakia was a state.
-
B.
postwarRedesignationOf
chosen
Indicates the relationship in which an entity receives a new designation or identity as a result of postwar changes or reorganization.
-
C.
historicalNameInSlovak
Indicates that an entity is known or referred to by a particular historical name in the Slovak language.
-
D.
czechName
Indicates that an entity has a name in the Czech language, specifying the Czech-language form of its name.
-
E.
AustrianDesignation
Indicates that an entity has an official designation, title, or status specifically within the Austrian context (e.g., by Austrian law, administration, or standards).
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.