Triple
T5876944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K9A2 |
E130648
|
entity |
| Predicate | hasOriginIndustry |
P19086
|
FINISHED |
| Object | South Korean defense industry |
—
|
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: South Korean defense industry | Statement: [K9A2, hasOriginIndustry, South Korean defense industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginIndustry Context triple: [K9A2, hasOriginIndustry, South Korean defense industry]
-
A.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
B.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
C.
hasParentCompanyIndustry
Indicates that an entity’s parent company operates in, or is associated with, a specified industry.
-
D.
isPartOfIndustry
chosen
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
-
E.
hasHistoricIndustry
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.