Triple
T233345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krupp Trial |
E4454
|
entity |
| Predicate | industryInvolved |
P71
|
FINISHED |
| Object | armaments 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: armaments industry | Statement: [Krupp Trial, industryInvolved, armaments industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryInvolved Context triple: [Krupp Trial, industryInvolved, armaments industry]
-
A.
industryEvent
Indicates that an event is related to a specific industry, such as a conference, trade show, or professional gathering focused on that industry.
-
B.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
-
C.
sector
chosen
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
D.
positionInIndustry
Indicates the role, rank, or standing that an entity holds within a particular industry or sector.
-
E.
supplyChain
Indicates a relationship where one entity participates in providing, transferring, or managing goods, services, or information to another as part of a sequential production and distribution process.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.