Triple
T26063214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mil Mi-60 |
E657324
|
entity |
| Predicate | designBureauSpecialization |
P62830
|
FINISHED |
| Object | helicopter development |
—
|
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: helicopter development | Statement: [Mil Mi-60, designBureauSpecialization, helicopter development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designBureauSpecialization Context triple: [Mil Mi-60, designBureauSpecialization, helicopter development]
-
A.
designBureau
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
-
B.
hasDesignExpertise
Indicates that one entity possesses specialized knowledge or skill in design related to another entity.
-
C.
designDiscipline
chosen
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
-
D.
creatorSpecialization
Indicates the specific field, discipline, or area of expertise in which a creator primarily works or is specialized.
-
E.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 26, 2026, 7:20 p.m.