Triple
T35783001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKEK |
E1034482
|
entity |
| Predicate | hasSubsidiaryOrFacilityType |
P201459
|
FINISHED |
| Object | ammunition plants |
—
|
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: ammunition plants | Statement: [MKEK, hasSubsidiaryOrFacilityType, ammunition plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiaryOrFacilityType Context triple: [MKEK, hasSubsidiaryOrFacilityType, ammunition plants]
-
A.
hasSubfacility
Indicates that one facility is a subordinate or component facility within another, larger facility.
-
B.
hasSubsidiariesIn
Indicates that an entity has subsidiary companies or organizations operating or registered in a specified location or jurisdiction.
-
C.
hasSubOrganizationType
Indicates that an organization is associated with or classified under a specific type or category of sub-organization.
-
D.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
E.
hasSubsidiaryBusiness
Indicates that one business entity owns or controls another business entity as its subsidiary.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
| PDg | Predicate description generation | batch_69fff86da6f48190aac10a80b648c05a |
completed | May 10, 2026, 3:15 a.m. |
Created at: May 3, 2026, 4:06 p.m.