Triple
T85659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Manpower Commission |
E1724
|
entity |
| Predicate | industryRegulated |
P2153
|
FINISHED |
| Object | war-related manufacturing |
—
|
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: war-related manufacturing | Statement: [War Manpower Commission, industryRegulated, war-related manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryRegulated Context triple: [War Manpower Commission, industryRegulated, war-related manufacturing]
-
A.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
B.
governmentInvolvement
chosen
Indicates that a government participates in, influences, regulates, or otherwise plays a role in the specified activity, process, or entity.
-
C.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
D.
economicClassification
Indicates how an entity is categorized based on its economic characteristics, status, or role within an economic system.
-
E.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24eb59e808190811c20518f39b1cc |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.