Triple
T25639471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazan Helicopters |
E642795
|
entity |
| Predicate | roleInMiSeries |
P175945
|
FINISHED |
| Object | major production center for Mi-8/17 family |
—
|
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: major production center for Mi-8/17 family | Statement: [Kazan Helicopters, roleInMiSeries, major production center for Mi-8/17 family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMiSeries Context triple: [Kazan Helicopters, roleInMiSeries, major production center for Mi-8/17 family]
-
A.
narrativeRoleInSeries
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
-
B.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
roleInAnime
Indicates that an entity holds a specific character role or participation in a particular anime work.
-
E.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
- 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_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 21, 2026, 5:38 p.m.