Triple
T25639470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazan Helicopters |
E642795
|
entity |
| Predicate | hasTypeCertificateFor |
P172084
|
FINISHED |
| Object | Ansat helicopter |
—
|
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: Ansat helicopter | Statement: [Kazan Helicopters, hasTypeCertificateFor, Ansat helicopter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeCertificateFor Context triple: [Kazan Helicopters, hasTypeCertificateFor, Ansat helicopter]
-
A.
certificateType
Indicates the specific kind or category of certificate associated with an entity or relationship.
-
B.
typeOfCertification
Indicates the specific kind or category of certification associated with an entity.
-
C.
hasSafetyCertificate
Indicates that an entity possesses or has been granted a valid safety certificate.
-
D.
hasCertificationLabel
Indicates that an entity bears or is associated with a specific certification label signifying compliance with defined standards or criteria.
-
E.
certificationBy
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 21, 2026, 5:38 p.m.